16 May 15:37
"Opportunistic locking" or "edit sequence"
From: Michael Hipp <Michael <at> Hipp.com>
Subject: "Opportunistic locking" or "edit sequence"
Newsgroups: gmane.comp.python.sqlalchemy.user
Date: 2008-05-16 13:38:37 GMT
Subject: "Opportunistic locking" or "edit sequence"
Newsgroups: gmane.comp.python.sqlalchemy.user
Date: 2008-05-16 13:38:37 GMT
Hello, new to SQLAlchemy. A question... Does SA implement what is sometimes referred to as opportunistic locking or sequence locking? This is intended to prevent near simultaneous but incompatible UPDATESs of the same record in the database by two different clients. Some databases implement this by using a field like 'edit_sequence' which is an incrementing sequence where the value in the db must match that in the UPDATE. Does SA have such a feature or something like it? Thanks, Michael Hipp Heber Springs, Arkansas, USA --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy <at> googlegroups.com To unsubscribe from this group, send email to sqlalchemy-unsubscribe <at> googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
RSS Feed