William R. Mussatto wrote:
> Rudy Lippan said:
>> On Fri, 25 Feb 2005, Jason Johnson wrote:
>> 
>>> 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). 
>>> 
>> 
>> Sounds like you need to get a copy of DBD::mysql that was compiled
>> against the  latest mysql client libraries.
> I ran into this problem a couple of months ago and the answer then was
> that MySQL had given the libraries to Active State but they had not
> pushed out the updates.  Since I didn't need the newer version, I
> went back to the version of Mysql which used the passwords that AS
> Perl did support.  I guess they still haven't pushed out the updates.
> 
        Just loaded MySQL 4.1 and am using AS 5.8.3-build 809. Reloaded DBI, 
DBD-ODBC and DBD-mysql. Failed as stated above with user/password.  Well I went 
and looked at the DBI info and found this;
ppm install http://theoryx5.uwinnipeg.ca/ppms/DBD-mysql.ppd
        which is as stated in the DBI Randy Kobes and I loaded it.  I then 
tried my simple script and it ran to conclusion.


Wags ;)


>>> 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)?
>> 
>> I don't know where you can find a copy of DBD::mysql linked against
>> the latest mysql client libraries. Maybe ActiveState might have
>> something, but I don't know. 
>> 
>> 
>> -r



*******************************************************
This message contains information that is confidential
and proprietary to FedEx Freight or its affiliates.
It is intended only for the recipient named and for
the express purpose(s) described therein.
Any other use is prohibited.
*******************************************************

Reply via email to