On Mar 4, 2011, at 5:09 PM, Lenza McElrath wrote: > > So there is no way to accomplish this in 0.6? I was looking at doing it the > way I describe above, but it is not trivial to figure out which model/session > a value is attached to. And I guess it is theoretically possible that a > value could be connected to two models/sessions. Definitely scared of moving > to an untested code... but looks like there are lots of improvements in 0.7 > that might make it worth it...
well, the on-change event required some less than trivial features so its an 0.7 thing. The best solution of all is to not use mutable types in the first place. I.e. if you need to change a scalar value in place, do something like myobject.value = value.mutate(xyz). > > > > -- > 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. -- 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.
