20be89b3b2
Changes since 2.2216 are missing, here is the changes from 1.2215 to 1.2216 : * Portability changes for mSQL 3 and MySQL 4. * Added transaction support for MySQL. (Bob Lyons <lyons@nextrials.com>) * dbd/dbdimp.c: Fixed MAXLENGTH warning; used to hint for a not existing mysql_maxlength, which should read mysql_max_length. (Paul DuBois <paul@snake.net>) * Fixed installation problem when a directory was specified, but did not exist. (Will Partain <partain@dcs.gla.ac.uk>) * Fixed that mysql_errno wasn't used properly. (Chris Adams <cmadams@hiwaay.net>) * Fixed test suite problem, when user name and password have been interpolated. (Bruno Hivert (LMC) <lmcbrhi@lmc.ericsson.se>) * mysql_insertid and mysql_affectedrows are no longer treated as integers, but longs. Thanks to Michael G Schwern <schwern@pobox.com>.
11 lines
595 B
Text
11 lines
595 B
Text
Mysql.pm and DBD::mysql implement two different approaches to
|
|
communicate with an mysql server. DBD::mysql is built upon the DBI,
|
|
the generic Perl Database Interface. It brings you an identical
|
|
interface to a broad variety of databases and is in this regard
|
|
comparable to ODBC.
|
|
|
|
The advantage of the DBI approach is portability and interoperability.
|
|
Mysql.pm is the elder species. It was written before DBI was
|
|
available but inspired by an early draft of the DBI specification.
|
|
As has been been circulating longer it are more mature and pretty
|
|
stable. It is also more complete than DBD::mysql.
|