Dear DBD::mysql developers,

DBD::mysql version 3.0007 (stable, production) and 3.0007_1 (dev) have
been released!

Version 3.0007 is the production version with server-side prepare
statements turned off by default, and 3.0007_1 is the development
version with server-side prepare statements turned on by default.

Changes in 3.0007/3.0007_1, from ChangeLog:

* Make sure to call dbd_st_finish when all rows from a statement handle
   have been fetched. (Bug #20153, Bug# 21607, as rt.cpan.org ticket #s
   20464, 21241) Jim Winstead
 * Patch from Steve Hay to fix bind_param to deal properly with insertion
   of a NULL into an INT or DOUBLE column using server-side prepare.
   Converted Steve's dbi.pl script to expose this problem to 40bindparam2
   test.
 * Fix to mysql_st_internal_execute to keep from passing undefined dbh
   handle member (bind_type_guessing) to parse_param causing crash on
   OpenBSD. Reported on rt.cpan.org (#20868) by Kyle Georg, as well as
   info from Sam Smith and Federico Giannici
 * Cleaned up tests to make sure test table is dropped at end of test.

Notes:

* To turn ON server-side prepared statements (only in 3.0007 non-dev
release),
simply append ";mysql_server_prepare=1" to the connect string or via the
driver
handle. Server-side prepared statements are turned off (emulated) by
default in 3.0007.
Please refer to documentation for further details.

* To turn OFF server-side prepare statements (only in 3.0007_1 dev
release) to have
emulated prepared statements, append ";mysql_emulated_prepare=1" in the
connect string or
via the driver handle. Server-side prepared statements are turned on by
default in 3.0007_1.
Please refer to documentation for further details.

* Very soon, I intend to turn on  server side prepared statement on by
default. I will test this thoroughly prior to making the switch,
so that users don't have any problems when upgrading, when the time comes.

* This prepared statement API is only available with MySQL server versions
4.1 and above, so if you're using an older version, you won't notice
anything.
Though, be assured that even for the driver emulated handling of prepared
statements, I will continue to make sure the code is improved.

As the community, one think you can do if you are interested in helping
is to turn on server side prepare statements in 3.0007, or try the
development driver, 3.0007_1 to see if there are any problems. I've
tested the code as much as I can, but I know nothing tests code like
1000s of developers thinking of unique ways of using the driver that I
never could have imagined. If you find a bug, please report it to me, or
at http://bugs.mysql.com. There is also the rt.cpan.org website for
reporting
issues, but I prefer http://bugs.mysql.com, since there is a good
verification
process when a bug is reported there, and it's more visible to me.

To this list in particular - those of you who would like to send patches and be able to contribute, please feel free to contact me with your CPAN info which I can give you SVN write access. It would be great to have more developers contributing to DBD::mysql!

Coveat: Please make sure you don't use a threaded Perl with this driver
on Solaris.

Again, if anyone has any problems or questions with the driver, please
feel free to email me, or especially post to [email protected] , and if
you find bugs, please report them to http://bugs.mysql.com

These versions for this module can be found at CPAN:

http://search.cpan.org/dist/DBD-mysql/

Again, thanks to all who helped to report bugs for this release and
provided patches.

Please feel free to email me directly if you need to get my attention to
something that needs
attention, as well as if you feel that you would like to contribute to
DBD::mysql.

Also, thank you for using MySQL and DBD::mysql!

Kind regards,

Patrick Galbraith

Reply via email to