On Mon, Jan 20, 2014 at 1:51 PM, Richard Gerd Kuesters <rich...@humantech.com.br> wrote: > i was having this kind of problem while using a multi-threaded app, but with > a postgres backend. > > in postgres, with high-concurrency, i was expecting this kind of behaviour, > so i had to implement some simple semaphores to make it work properly -- > sqlalchemy is not to blame if something changes in your database while one > end of a software creates a record that the another doesn't knows about when > trying to operate on.
I think it may have something to do with the implicit transaction the session opens when manipulated. P2 may be holding on to an older snapshot. I'd suggest committing right before checking to see whether the records are there in P2, just as an experiment. The right behavior would be to commit after any kind of session manipulation, though that's trickier (lots of things count as implicit session manipulations). -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
