Jonathan Ellis wrote:
On 4/12/06, *Michael Bayer* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
OK, what Hibernate capabilities would we *not* want to support
? Keeping
in mind I am only somewhat familiar with Hibernate myself, so
maybe theres
plenty.
I am also not a hibernate expert. (If it were easy to become one, we
wouldn't be having this discussion. :)
But one part I would be very leery of is the inheritance support.
Especially since in Python there are so many other ways to re-use
code; in Java inheritance is basically your only option there, but in
Python composition is much better supported (via __getattr__) and of
course you also have monkeypatching. These are acceptable
workarounds, I think, for people whose uses don't fit the existing SA
inheritance support (which IMO best fits the relational model, vs the
other hibernate options).
I have used Hibernate quite extensively. I have to agree here. Of all
the schema in my current databases modeled by hibernate, the tables
mapped to support an inheritance model are the least intuitive to use
with standard "simple" sql (Be it via subclass=joined, or
subclass=discriminator or whatever) If I were to have started at the
database instead of the modeling layer, I'd have never designed the
schema that way.
-Dennis
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
