>>> [EMAIL PROTECTED] 04/07/04 6:11 AM >>> >> 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. But really, how difficult is that? IMO, we are talking about 5 minutes either way. IMO, the time is not in the code, but rather in the testing. With iBATIS, you can find where the modified sqlmaps are being used. In Hibernate, you can not because it is all done behind the scenes, especially in the case of... > lazy loading ...which has been in iBATIS for a long time. You can define those in your sql map and it will do it just fine. :-) Larry --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
