Metadata-Version: 1.0
Name: Products.ZMySQLDA
Version: 5.4.7dev-r43182
Summary: ZMySQLDA Product This is the Z MySQL database adapter product for the Z Object Publishing Environment.
Home-page: http://svn.erp5.org/erp5/trunk/products/ZMySQLDA
Author: NEXEDI SA
Author-email: info@nexedi.com
License: UNKNOWN
Description: Z MySQL DA
        
        This is the Z MySQL database adapter product for the
        Z Object Publishing Environment.
        
        ** NOTE **
        
        Note that the Z MySQL database adapter is compatible with MySQL
        versions 3.22 and later (including MySQL 3.23).
        
        ** IMPORTANT **
        
        This product is distributed as a NON-BINARY release!
        
        This product requires compiled Python extensions that are
        NOT included as a binary with this release. You must build
        or install the required extensions using the instructions
        below before the product will work properly!
        
        Installation
        
        The Z MySQL database adapter uses the MySQLdb package.
        This must be installed before you can use the Z MySQL DA.
        You can find this at::
        
        http://sourceforge.net/projects/mysql-python
        
        You need at least version 0.9.0. If you are compiling this
        yourself, you must use the same python executable as your
        Zope installation uses, otherwise Zope will not find it.
        
        Connection Strings
        
        The connection string used for Z MySQL Database Connection
        are of the form::
        
        database[@host[:port]] [user [password [unix_socket]]]
        
        or typically just::
        
        database user password
        
        to use the default server.
        
        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.
        
        
Keywords: Zope ZMySQLDA
Platform: UNKNOWN
Classifier: Framework :: Zope2
Classifier: Operating System :: OS Independent
