diff options
| author | adustman <adustman@9fc6cd9a-920d-0410-adcf-ac96716ed7e8> | 2002-02-25 05:48:31 +0000 |
|---|---|---|
| committer | adustman <adustman@9fc6cd9a-920d-0410-adcf-ac96716ed7e8> | 2002-02-25 05:48:31 +0000 |
| commit | 4b912f7650c60635d484a5a57f5c7d86fa193f38 (patch) | |
| tree | 99b48128d5dcdf396580c73696229c0d63b69b98 | |
| parent | 24081f4e131f250d3f314cec642c0b27817bd45d (diff) | |
| download | mysqldb1-4b912f7650c60635d484a5a57f5c7d86fa193f38.tar.gz | |
changelog
| -rw-r--r-- | ZMySQLDA/lib/python/Products/ZMySQLDA/CHANGES.txt | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/ZMySQLDA/lib/python/Products/ZMySQLDA/CHANGES.txt b/ZMySQLDA/lib/python/Products/ZMySQLDA/CHANGES.txt index d65a155..8229faa 100644 --- a/ZMySQLDA/lib/python/Products/ZMySQLDA/CHANGES.txt +++ b/ZMySQLDA/lib/python/Products/ZMySQLDA/CHANGES.txt @@ -6,7 +6,16 @@ Z MySQL DA Releases Wrap queries with a lock to prevent multiple threads from using the connection simultaneously (this may or may not be happening). - If transactional, then the lock is held for the entire transaction. + If transactional, then there is an additional transaction lock, + acquired at the beginning of the transaction and released when + either finished or aborted. + + A named lock can be specified by inserting *LOCKNAME at the start + of the connection string. This is probably best used only if you + must use non-transactional tables. + + Some stuff will be logged as an error when bad things happen + during the transaction manager hooks. 2.0.8 |