The documentation says: "As far as the issue of the same object being modified in two different Sessions, that's an issue of concurrency detection; SQLAlchemy does some basic concurrency checks when saving objects, with the option for a stronger check using version ids. See None for more details."
Using ORM of course: I don't want an object such as "query.get(2)" in two different threads in two different sessions to be changed if one of them changes. Especially when transactions are in use. I.e. two different threads are for two different people who are oblivious to each other and if there is a conflict, one of their transactions will be rejected. I tried it and it seems ok, but if it is a planned feature i wish to know about it. Also, is it possible to do: * SAVEPOINT as in PostgreSQL. http://www.postgresql.org/docs/current/static/sql-savepoint.html * choose the manner of transactions, i.e. serializable, ... what is the default transaction mode for SQLAlchemy? in postgresql if you choose serializable your transaction can fail and you are in charge or restarting it. Finally, when operations are done on a session. when i do session.flush() are they guaranteed to be performed in order? at least when i use transactions. 10x. -- Regards, Tzahi. -- Tzahi Fadida Blog: http://tzahi.blogsite.org | Home Site: http://tzahi.webhop.info WARNING TO SPAMMERS: see at http://members.lycos.co.uk/my2nis/spamwarning.html Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
