Thanks for the quick response. On 9/24/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > but also i dont understand the problem you're having. the > ConcurrentModificationError should only happen if you are issuing a > literal DELETE statement to the database which conflicts with the > session trying to delete the instance, or if you've already issued > the delete and flushed in a session concurrent to the current one.
yes, this was exactly what I was doing, whoops. When I changed it to only flush once I was painfully reminded that my regression suite was failing in mysterious ways because I didn't have any relation properties assigned to my mappers (it looked like the parent object wasn't getting saved). At the time I couldn't figure that out. Sigh. But, yes, putting flush in the right place made the newer code work :) Now I have what appears to more misconfigured mapper issues but those should be easy to find answers to. I'd just been staring at it all too long to notice the multiple flush calls. Thanks! -Kumar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
