Re: [sqlalchemy] object changes

2011-02-19 Thread Alexander Solovyov
On Sat, Feb 19, 2011 at 03:28, Michael Bayer wrote: > So there is attributes.get_history(obj, key) as the public API, so you don't > have to mess around with states and dicts and such.   It accepts an argument > "passive" which when passed the symbol attributes.PASSIVE_NO_INITIALIZE will > not

Re: [sqlalchemy] object changes

2011-02-18 Thread Michael Bayer
So there is attributes.get_history(obj, key) as the public API, so you don't have to mess around with states and dicts and such. It accepts an argument "passive" which when passed the symbol attributes.PASSIVE_NO_INITIALIZE will not fire off any lazy callables, including those collections you

[sqlalchemy] object changes

2011-02-18 Thread Alexander Solovyov
Hi, what's the right way to detemine what changed on an object? I use ext.declarative and mapper extension, which calls code in the end of message after_insert and before_update. It skips M2M relations because .get_history() call loads everything in memory. Is there better way to determine what's