[SQL-CVS] r3237 - SQLObject/branches/0.9/docs
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: <sub...@co...> - 2008-02-01 14:46:34
|
Author: phd Date: 2008-02-01 07:46:26 -0700 (Fri, 01 Feb 2008) New Revision: 3237 Modified: SQLObject/branches/0.9/docs/SQLObject.txt Log: cacheValues can be used with transactions. Modified: SQLObject/branches/0.9/docs/SQLObject.txt =================================================================== --- SQLObject/branches/0.9/docs/SQLObject.txt 2008-02-01 14:46:06 UTC (rev 3236) +++ SQLObject/branches/0.9/docs/SQLObject.txt 2008-02-01 14:46:26 UTC (rev 3237) @@ -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 - implied). + do so. `registry`: 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` -off, like:: - - 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:: Person.select(Person.q.name=="value", forUpdate=True) |