From: <sub...@co...> - 2006-09-26 12:21:12
|
Author: phd Date: 2006-09-26 06:21:09 -0600 (Tue, 26 Sep 2006) New Revision: 1949 Modified: SQLObject/docs/News.txt SQLObject/docs/SQLObject.txt Log: SELECT FOR UPDATE. Modified: SQLObject/docs/News.txt =================================================================== --- SQLObject/docs/News.txt 2006-09-26 12:08:10 UTC (rev 1948) +++ SQLObject/docs/News.txt 2006-09-26 12:21:09 UTC (rev 1949) @@ -47,6 +47,8 @@ * New joins! ManyToMany and OneToMany; not fully documented yet, but still more sensible and smarter. +* SELECT FOR UPDATE + Small Features -------------- Modified: SQLObject/docs/SQLObject.txt =================================================================== --- SQLObject/docs/SQLObject.txt 2006-09-26 12:08:10 UTC (rev 1948) +++ SQLObject/docs/SQLObject.txt 2006-09-26 12:21:09 UTC (rev 1949) @@ -1292,13 +1292,11 @@ If you want to begin a new transaction after a .rollback() call .begin(). -If you want to use transactions you should also turn `_cacheValues` -off, like: +You can use SELECT FOR UPDATE in those databases that support it:: - class Person(SQLObject): - _cacheValue = False - # ... + Person.select(Person.q.name=="value", forUpdate=True) + Automatic Schema Generation --------------------------- |