On May 19, 2008, at 3:40 PM, TP wrote:
> > Yeah, can do it on top, but for various reasons I was hoping there was > some sort of interface that would let me interpose code before inserts > were executed and then I could grab the insert and queue it for later > rather than have it execute now. Sounds like the ProxyConnection may > let me do this. > >> when the Session goes to insert/update/delete a row, thats not a passive operation, it gets back data in all cases - either the newly generated primary key, or the count of rows affected. it definitely needs the PK value in order to place things in its identity mapping. So im not sure how you'd "defer that for later". It also has a transactional model that would totally go out the window if the things it were issuing weren't actually happening. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
