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).
Then of course there's Hibernate caching, but I'm less nervous about that given your previous posts on that subject.
Finally there's the whole session and threadlocal stuff, which I'm already kind of nervous about in SA. I admit that I don't understand the use cases here, but my gut feeling is I'd prefer a simpler approach that let the user handle threading issues: if you want a separate connection for thread B, grab one. If you want the same one as in thread A, use that. Explicit is better than implicit, right? :)
--
Jonathan Ellis
http://spyced.blogspot.com
