On Oct 3, 2012, at 10:34 AM, Michael Bayer wrote: > > > Catching both of these is easy enough and a patch is added to #2583: > http://www.sqlalchemy.org/trac/ticket/2583 > > The SQLite case you describe isn't exactly like either of these; if the > object were flushed by the session and received the same PK, that case is > already handled since the object would be in ._new. So my only guess is > that, that's not the trigger of the issue. So at the very least you need > to try that patch and see if it clears things up. > > Assuming that's the fix, I don't know that there's a clean way to patch this > in, except for patching your install or monkeypatching a new Session class > in. I should have it committed in both 0.7/0.8 within 30, unless I hit > some snags in the tests.
OK those are in tip for default + 0.7, so you can get those fixes now from the snapshot releases. -- 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 sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
