Originally posted by Gaurav Jain:
According to my understanding in hibernate each table is mapped to a POJO that means you will end up creating 250 POJO's and i am not sure how many config files will be created.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
If you used DAOs with hand-coded JDBC, where would you store the results for passing to the client? Wouldn't you create POJOs for this anyway?Originally posted by Gaurav Jain:
I am still not convinced that how hibernate is more advantageous over DAO especially when you talk about in excess of 250 tables.According to my understanding in hibernate each table is mapped to a POJO that means you will end up creating 250 POJO's and i am not sure how many config files will be created.
Originally posted by Gaurav Jain:
I am still not convinced that how hibernate is more advantageous over DAO especially when you talk about in excess of 250 tables.According to my understanding in hibernate each table is mapped to a POJO that means you will end up creating 250 POJO's and i am not sure how many config files will be created.
I am yet to find out a sure shot winner in terms of hibernate...
Cheers, Sathya Srinivasan - SCJP 1.2, SCWCD 1.2, SCMAD 1.0
Co-Author of Whizlabs SCMAD Certification Exam Simulator and SCMAD Exam Guide Book
Originally posted by Gaurav Jain:
I understand that hibernate generates HQL in the background.If i need to fine tune my SQL queries then how do i do them since those are HQL's generated by hibernate although tuning is possible if the developer writes the normal SQL himself.
Originally posted by Gaurav Jain:
I dont think you can write HQL yourself..
Consider Paul's rocket mass heater. |