On Sat, Feb 18, 2012 at 07:57:14PM -0500, Michael Bayer wrote: > I don't know that customizing instrumentationmanager is all you'd need. > There's lots of bookkeeping occurring with instancestate that takes time and > is related to state tracking and persistence. The whole need for > __setstate__ is due to the instancestate object. Not including it suggests > an entirely new system that at most would consume rows from the orm.Query and > route them into this alternate system.
Well, I didn't want to implement entirely new system, but just to separate part of ORM which manages persistence from part of ORM which just map database columns to instance attrs. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
