Date: 2008-02-01 07:48:56 -0700 (Fri, 01 Feb 2008)
New Revision: 3239
cacheValues can be used with transactions.
--- SQLObject/trunk/docs/SQLObject.txt 2008-02-01 14:48:39 UTC (rev 3238)
+++ SQLObject/trunk/docs/SQLObject.txt 2008-02-01 14:48:56 UTC (rev 3239)
@@ -706,8 +706,7 @@
object the database will be queried for a value, i.e., a ``SELECT``
will be issued. If you want to handle concurrent access to the
database from multiple processes then this is probably the way to
- do so. You should also use it with transactions_ (it is not
+ do so.
Because SQLObject uses strings to relate classes, and these
@@ -1369,16 +1368,6 @@
.begin(). The last .commit() should be called as .commit(close=True) to
release low-level connection.
-If you want to use transactions you should also turn `_cacheValues`
- class Person(SQLObject):
- _cacheValue = False
-This, though, makes attribute access very slow (SQLObject queries database
-for an every attribute access). If one wants to set `_cacheValue = True`
-one has to synchronize objects between threads herself.
You can use SELECT FOR UPDATE in those databases that support it::
Get latest updates about Open Source Projects, Conferences and News.