Barney
Dumb question, but is this in response to the error message you got
where at the end of the error it asks you to "update your client
program"? If so it is referring to the PHP code not the actual
PHP/MYSQL/APACHE programs..... you need to update your PHP code to work
with the updated MYSQL authentication method.
Hope this helps....even a little.
Regards
Jeremy
www.bluejayspc.co.uk
barney wrote:
Folk,
Just installed MySQL 4.1.14 on a new Windows XP Pro system - this is a
development system, no domain. Also installed PHP 4.3.11 and Apache 2.0.55.
so now I have WAMP, right? Apache works fine as the web server; PHP works
fine, as well.
As soon as I tried to access databases created with MySQL 3.23.x, I got the "Client
does not support authentication ..." error.
I finally corrected by updating the 'user' table with the OLD_PASSWORD()
function, and was able to access the databases. Using old_password() in the
config file did not work.
My question(s) follow.
Since this is a new install, why is the client still 3.23.49? This was a virgin
disk as far as Apache, MySQL & PHP were concerned. Previous experience has
shown that I can uninstall MySQL and reinstall and still have the same client
version. That's why I did the 'wipe disk, reinstall XP, reinstall everything else'
bit.
Where can I find a later version of the client? I've searched the web docs
'til I'm cross-eyed, but every time I've found any reference to a later client,
the discussion has immediately advanced to C jargon and compiler issues. I'm
not C/C++ capable - I can hold my own with VB and some scripting languages, but
C is a bit esoteric for me - comprehension problem, I guess.
Mostly, why does this error occur on a fresh install? The databases I accessed
know nothing of authentication - haven't been developed to that point. Yeah, I
know ... it's a Windows system. But I don't buy that one, not in this
instance. Maybe because the current default table format is InnoDB and the old
format was MyISAM?
Upgrade to PHP 5.x - I've seen references to that curing the problem - is not
an option. I need to have the same configuration as exists on the server that
will be used once development is done.
One last question ... what happens when I build new databases/tables? Or
assign database users for upkeep, maintenance, replication, whatever? Which
password format will be used then?
I'd appreciate any help ... or even conjecture, at this point <chortle />.
Make a good day ...
... barn
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
