[sqlalchemy] Re: Concurrent Update Errors

2009-09-17 Thread gizli
Thanks for the excellent information Michael. Will need to think about this and post again if I have further questions. As for the delete/rm discussion, I guess it depends on your use case. I usually run rm with -f flag which fails silently if no file is found. But I get your point and you also p

[sqlalchemy] Re: Concurrent Update Errors

2009-09-17 Thread Michael Bayer
gizli wrote: > > t1.delete(obj) > t2.delete(obj) > t2.commit() > t1.commit() I also forgot to mention that you can always use query.delete() or table.delete() to get a standard "relational" delete, though it does not offer in-python cascading. This delete translates directly to DELETE with the g

[sqlalchemy] Re: Concurrent Update Errors

2009-09-17 Thread Michael Bayer
gizli wrote: > > Hi guys, > > I have a couple of questions about a recent concurrency test I did on > SA. Someone in our team ran into a very intermittent issue where a > certain operation he tried doing failed by ConcurrentUpdateError. I > wrote a simple thread that can do query/update/insert/com