[z3-checkins] r5577 - z3/sqlos/trunk

[faassen at codespeak.net]

Author: faassen
Date: Wed Jul 14 19:54:17 2004
New Revision: 5577

Modified:
   z3/sqlos/trunk/README.txt
Log:
Dedent more to make better ReST.


Modified: z3/sqlos/trunk/README.txt
==============================================================================
--- z3/sqlos/trunk/README.txt	(original)
+++ z3/sqlos/trunk/README.txt	Wed Jul 14 19:54:17 2004
@@ -227,26 +227,25 @@
 
 Our solution consists of:
 
- - Create a SQLObjectTransactionManager that implements
-   IDataManager. This object will keep track of the dirty objects for
-   a transaction.
-
- - Anytime a SQLObject-based object gets its ``dirty`` bit set, the
-   object is registered with the current SQLObjectTransactionManager.
-
- - If an object gets it's dirty bit set to ``False``, it may mean that
-   this object's ``sync()`` method has been called. We *could* call
-   ``sync()`` on all the dirty objects registered before, but this
-   would increase complexity a lot. For now, we just recommend *not*
-   calling ``sync()`` or ``syncUpdate()`` manually inside
-   transactions.
-
- - SQLObjectTransactionManager needs to have a ``sortKey()`` that
-   returns a value smaller than ZopeDBTransactionManager's (which
-   currently doesn't implement this method, so
-   ``id(<ZopeDBTransactionManager>)`` is used). This is so that the
-   ``UPDATE`` queries get sent before the RDB cursor's ``commit()`` is
-   called.
+- Create a SQLObjectTransactionManager that implements
+  IDataManager. This object will keep track of the dirty objects for a
+  transaction.
+
+- Anytime a SQLObject-based object gets its ``dirty`` bit set, the
+  object is registered with the current SQLObjectTransactionManager.
+
+- If an object gets it's dirty bit set to ``False``, it may mean that
+  this object's ``sync()`` method has been called. We *could* call
+  ``sync()`` on all the dirty objects registered before, but this
+  would increase complexity a lot. For now, we just recommend *not*
+  calling ``sync()`` or ``syncUpdate()`` manually inside transactions.
+
+- SQLObjectTransactionManager needs to have a ``sortKey()`` that
+  returns a value smaller than ZopeDBTransactionManager's (which
+  currently doesn't implement this method, so
+  ``id(<ZopeDBTransactionManager>)`` is used). This is so that the
+  ``UPDATE`` queries get sent before the RDB cursor's ``commit()`` is
+  called.
 
- - Create a SQLOS class that subclasses SQLObject to override
-   ``dirty`` and enable lazy updates by default.
+- Create a SQLOS class that subclasses SQLObject to override ``dirty``
+  and enable lazy updates by default.