On 2010-01-28 19.13, Alex Shneyderman wrote:
get more widespread usage. Yes, it is suboptimal, yes it will be more work
to use, but there it is. Also, several people told me not to try and base
our RDBMS support on Hibernate, as they claimed it was basically broken in
terms of semantics.
What are the concrete problems with hibernate? "it was basically
broken in terms of semantics" - what does this mean? What semantics
are we talking about here?
One of the issues were with how version numbers are handled with
many-many associations. I don't recall all the details right now, but
essentially if you changed an association on one side, it effected the
other side to the point where you would get a lot of (seemingly)
unnecessary failed transactions under high load because of versioning
issues. Also, Hibernate didn't seem to handle complex value objects
well, which is a problem. In general many developers seem to favor
making everything entities, because Hibernate prefers it that way.
There were other stories about problems with the cache system, that were
severe enough to question whether it is useful at all.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
