On 14/07/10 23:16, Moandji Ezana wrote:
[...]
And that is not easy and sometimes not nice either (did someone
mention "object identity" yet?). That makes Hibernate a solution
that is nice and easy as long as you either don't care at all
about the potential issues or you have someone else to take care.
If you are the one who has to care you really need a very good
understanding of the OO side, the RDB side and the ORM part.
n their defense, they do say that Hibernate is not a replacement for
knowing how databases work. And couldn't you say the same of Grails
and Rails? Grails especially, as it uses Hibernate.
Hibernate as an implementation is not all that bad. It has issues, in
particular with error reporting, but the real problem is the idea of ORM
not Hibernate in particular.
So: yes, I would say the same of Grails and Rails, and Grails in particular.
Peter
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to javapo...@googlegroups.com.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
