> > > yeah using the Connection to issue SQL is the intended usage of > after_insert()/after_update(), as long as its not SQL that might > affect future SQL within the flush itself (like, deleting a row that > the ORM is going to want to update or delete itself). >
great, that makes sense. Thanks for adding the post-SQL events, they're very handy. assuming you mean two foreign keys that reference mutual tables, if > you have relations() set up for these FKs, this is what the > post_update flag is intended to do for you. these are actually on the same table as the PK, and they have a funky one-to-one relation. Pretty small usecase and the post-insert hook works fine for me. As long as that is supported, I'm good with that. Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
