> Just to be up front, I will tell you now that I am NOT an O/R fan. :-)
I think that when you have 50 tables in your db and your app is just a big gui front end Hibernate is very good. Suppose in one of this 50 tables a field is added. With iBatis you have to re-write 4 methods (update, insert, delete, select), while with hibernate you just have to add the field to your xml mapping file. Another thing that is fantastic: lazy loading. Suppose you have a master detail relationship. In hibernate you can do: select master from master to get a list of master. Then whenever you access the list of "details" hibernate will issue the query for you: 1) select master from master (details not loaded yet, so no hits to the db) 2) (in java code) myMaster.getDetails()[1].getName(); -> hibernate automatically hits the db to retrieve the list of details While with others methods (ex: iBatis) you have to write a method like List getDetailsFromMaster(Master master) But, as I said, don't use Hibernate if you are going to do massive insert/delete work... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
