MySQL 4.1.10 + DBD-MySQL 2.9003 Incompatibility
From: Jason Johnson (jason_at_period-three.com)
Date: 02/25/05
- Previous message: Tom Mornini: "Re: how to fetch all records"
- Next in thread: Rudy Lippan: "Re: MySQL 4.1.10 + DBD-MySQL 2.9003 Incompatibility"
- Reply: Rudy Lippan: "Re: MySQL 4.1.10 + DBD-MySQL 2.9003 Incompatibility"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: dbi-users@perl.org Date: Fri, 25 Feb 2005 13:15:45 -0500
Note: I posted this on another list a few minutes ago only to realize
seconds after posting that it wasn't the right list. So if you are
subscribed to that list also and see this as a duplicate, I apologize
in advance.
I am running MySQL 4.1.10 and ActivePerl 5.8.6.811 on Windows 2003.
When I upgraded MySQL from an older version, everything using DBD-MySQL
complained about not being compatible and MySQL is telling me to
upgrade to a newer client (in this case, obviously, my client being
DBD-MySQL).
Does anyone know which version I should be using of DBD-MySQL and in
what repository I might find it? If so, how do I go about installing it
with PPM (I've installed may different packages using PPM, just curious
if there is any particular thing I may need to do when upgrading
DBD-MySQL)?
A side note, I had this same problem with PHP4, when I upgraded to PHP5
and tossed PHP's dll of the MySQL libraries in the correct location,
everything worked fine. This is why I must assume that there is a
DBD-MySQL package that has the correct implementation for the new
version of MySQL.
Any help would be much appreciated.
Thanks in advance,
Jason
- Previous message: Tom Mornini: "Re: how to fetch all records"
- Next in thread: Rudy Lippan: "Re: MySQL 4.1.10 + DBD-MySQL 2.9003 Incompatibility"
- Reply: Rudy Lippan: "Re: MySQL 4.1.10 + DBD-MySQL 2.9003 Incompatibility"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|