we've now got a Session object (dan's idea) , a Query object (dan's idea), we're using session.flush() pretty soon (my idea), and after 0.1.6 that is probably the end of the 0.1 series....0.2 will have a lot more scoping mods, with thread-local scope being just an optional case (dan's idea) and it will be very trivial for querying to be performed off the Session object rather than the Mapper, i.e. session.query(myclass, foo=bar) (like hibernate)... also, the name "private" apparently is something I read during a brief trip to an alternate universe since I was 100% sure I didnt come up with that name on my own...but you go to Hibernate, and its called "cascade"...how can we resist that name? (also FYI - "private=True" seems to correspond most closely to cascade="all-delete-orphan") plus theres the "version_id" parameter, the "entity_name" parameter i sneaked in there recently, the "polymorphic" thing that doesnt work so great...
at the point at which SA is looking more like Hibernate than you want it to, its time to speak up ! at the moment, Hibernate is partially or fully driving just about every decision made in the past three weeks. its gravitational pull is much stronger than that of trying to re-invent each concept on your own. Jonathan Ellis wrote: > On 4/12/06, Michael Bayer <[EMAIL PROTECTED]> wrote: >> >> it seems like "port hibernate!" is where SA is going > > > Please don't scare the children like that! :) > > -- > Jonathan Ellis > http://spyced.blogspot.com > ------------------------------------------------------- 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
