> specifically the lazy loader will work in the "after_flush_postexec()" > phase of the sessionextension. during after_flush(), the post-flush > bookkeeping has not been establishsed yet on assigned_to_id, and the lazy > loader always looks for the "persisted" version of the attribute.
ok, this explains my example in fact, that really means I cannot use that relation in after_flush. after_lush_postexec is too late as I need session.dirty/session.new to be able to understand what happened and take actions consequently. thanks sandro --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
