Hello,

2.9001 is here, almost.  I have incorporated the suggestions made by Tim 
WRT to the ChangeLog, auto_reconnect and failed_auto_reconnects. But 
before I send this up to CPAN, I would like to get a little feedback If 
anyone sees any problems, please let me know.

If everything looks good, I expect to upload this to CPAN on Tuesday 
afternoon (EST).

You can pick up a copy here: 
http://www.remotelinux.com/rlippan/DBD-mysql-2.9001.tar.gz

TIA,
Rudy


Changes:

2003-06-22  Rudy Lippan  <[EMAIL PROTECTED]> (2.9001)
        * moved pod into mysql.pm from mysql.pod
        * Changed the default behaviour of mysql_found_rows, so now
          'UPDATE table set field=?' will return the number of rows 
matched
          and not the number of rows physically changed. You can get the 
old
          behaviour back by adding "mysql_found_rows=0" to the dsn passed
          to connect.
        * Updated type_info_all() to be more inline with 
          what DBD::ODBC returns.
        * Added attribute 'auto_reconnect' that allows the auto reconnect
          behaviour to be toggled. :

          ** NOTE** The behaviour of auto reconnect has changed.  If
          either the MOD_PERL or the GATEWAY_INTERFACE environment 
variable is
          set, auto_reconnect will default to ON; otherwise auto_reconnect
          will default to off.  Earlier versions of this driver would 
always
          try to reconnect to the database on error; however, this is 
dangerous
          because table locks could be lost without the application 
knowing.

        * Fixed a segfault with failed reconnects that were trapped in an
          eval. The next tine DBD::mysql tried to reconnect, the process
          would segfault.
        * Added statistics attribute, 'mysql_dbd_stats' which returns
          a hash ref that contains 2 keys 'auto_reconnects' and
          'failed_auto_reconnects'.
        * Fixed bug where strings that were used in numeric
          context were not getting quoted on execute(). Now all
          parameters are bound as varchar by default.

          **NOTE** this is a change in behaviour that MAY cause problems
          with some SQL statements. If quoted integers, for example,
          cause any problems, use bind_param(<column_id>, SQL_INTEGER) to
          force a column to be bound as an integer.

        * Added get_info() method. See 'perldoc DBI' for more info
        * Added column_info(). See 'perldoc DBI' for more info [Tim Bunce]

Reply via email to