Hey, Michael Bayer wrote: > OK now that I see it, here's some things I think would make it more > generally useful: > > 1. lets split it into after_bulk_update() and after_bulk_delete(), so > that we can identify what operation just occured > 2. lets pass the Query object and the QueryContext in so that more > elaborate extensions can augment the functionality of the methods > 3. im a little torn on if the method should be called before or after > the "invalidation" logic kicks in, but im leaning towards "after" at > the moment.
Implemented this way now, and (boldly) committed to the trunk. :) Regards, Martijn --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
