Thanks. Does that full list of elements include individual instance attributes or just instances?
What happens if the before_update of an instance, the handler modifies a column on that same instance that is being saved? Is that also tracked via UOW, or via a compare against saved original values? On 3/29/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > theyre tracked as changed but the unit of work has already figured > out the full list of elements it wants to save (remember that it has > alraedy built up the full order of operations using a dependency sort). > > if you want to affect the list of elements to be saved you might want > to do that prior to the flush() (you can also subclass Session to > just decorate the flush() procedure). > > alternatively you could attempt to call the save_obj() method > directly on the desired mapper, that would be a little more > adventurous (particularly if youre not sure if your additional > objects may have already been saved in that flush, leading to double > operations). > > if neither of the above work we could attempt to stick a hook in > there somehow at the point at which UOW is figuring out what should > be saved. > > On Mar 29, 2007, at 3:02 PM, Rick Morrison wrote: > > > If a mapper extension modifies an attribute of an instance (the > > same instance being saved) in a before_insert() or before_update() > > call, are those attributes tracked as "changed" so they'll be > > included in the update? > > > > If not, is there any way to mark those items as changed? > > > > Thanks, > > Rick > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
