From 4b912f7650c60635d484a5a57f5c7d86fa193f38 Mon Sep 17 00:00:00 2001 From: adustman Date: Mon, 25 Feb 2002 05:48:31 +0000 Subject: changelog --- ZMySQLDA/lib/python/Products/ZMySQLDA/CHANGES.txt | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) 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 -- cgit v1.2.1