CHANGES.txt 2.37 KB
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66
Z MySQL DA Releases 2.0.9 Allow the connection string to work without a specified database. Wrap queries with a lock to prevent multiple threads from using the connection simultaneously (this may or may not be happening). 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 More information about columns is available from the table browser. This is primarily to support SQL Blender. DECIMAL and NUMERIC columns now returned as floating-point numbers (was string). This has also been fixed in MySQLdb-0.9.1, but the fix is included here just in case you don't upgrade. Upgrading is a good idea anyway, because some memory-related bugs are fixed, particularly if using Zope 2.4 and Python 2.1. 2.0.7 Transaction support tweaked some more. A plus (+) or minus (-) at the beginning of the connection string will force transactions on or off respectively. By default, transactions are enabled if the server supports them. Beware: If you are using non-TST tables on a server that supports transactions, you should probably force transactions off. 2.0.6 This version finally should have all the transaction support working correctly. If your MySQL server supports transactions, i.e. it has at least one transaction-safe table (TST) handler, transactions are enabled automatically. If transactions are enabled, rollbacks (aborts) fail if any non-TST tables were modified. 2.0.5 Transactions don't really work right in this and prior versions. 2.0.4 INT columns, whether UNSIGNED or not, are returned as Python long integers to avoid overflows. Python-1.5.2 adds an 'L' to the end of long integers when printing. Later versions do not. As a workaround, use affected columns with a format string, i.e. '<dtml-var x fmt="%d">'. 2.0.0 This is the first version of the database adapter using MySQLdb for Zope. This database adapter is based on the Z DCOracle DA version 2.2.0.