Permalink
Browse files

Fix documentation for @db_write

  • Loading branch information...
1 parent eec77c9 commit 7b616296fe31767af5d9d29cefb114a83e01b8f9 Antonis Christofides committed Nov 15, 2012
Showing with 5 additions and 8 deletions.
  1. +5 −8 README.rst
View
@@ -53,15 +53,12 @@ Caveats
``PinningRouterMiddleware`` identifies database writes primarily by request
type, assuming that any ``POST`` request is a write. You can indicate that
-any view triggers a database write by using the ``multidb.db_write`` decorator.
-You can also manually set ``response._db_write = True`` to indicate that a
-write occurred. Either one of these will cause the same result as if the
-request was a ``POST``.
+any view writes to the database by using the ``multidb.db_write``
+decorator. This will cause the same result as if the request was a ``POST``.
-This package makes no attempt to redirect database activity that occurs after a
-write but during the same request. You application is responsible for manually
-directing such activity to ``default`` with, for instance, the ``using`` method
-or keyword argument.
+You can also manually set ``response._db_write = True`` to indicate that a
+write occurred. This will not result in using the ``default`` database in this
+request, but only in the next request.
Configuration
=============

0 comments on commit 7b61629

Please sign in to comment.