exporting tables with password fields

>I am making a copy of a dB on my local machine so I can work on the
>interface. But the username/password combination -- which works on the
>"live" site -- doesn't work on my local machine. Is there something
>about the PASSWORD() fxn in mysql that is specific to the installation?

Just copying the dB doesn't copy permissions to use it. Did
you GRANT appropriate permissions? PASSWORD() changed a couple of
times in different versions but if you're using the same version on
both it shouldn't matter. What's the length of the result of PASSWORD()
on each system? As I recall two variants of the length are 16 and 41.
Try SELECT PASSWORD('foo') on both systems.

Gordon L. Burditt
 >> Stay informed about: exporting tables with password fields 

Gordon Burditt wrote:
>>I am making a copy of a dB on my local machine so I can work on the
>>interface. But the username/password combination -- which works on the
>>"live" site -- doesn't work on my local machine. Is there something
>>about the PASSWORD() fxn in mysql that is specific to the installation?
>
>
> Just copying the dB doesn't copy permissions to use it. Did
> you GRANT appropriate permissions? PASSWORD() changed a couple of
> times in different versions but if you're using the same version on
> both it shouldn't matter. What's the length of the result of PASSWORD()
> on each system? As I recall two variants of the length are 16 and 41.
> Try SELECT PASSWORD('foo') on both systems.
>
> Gordon L. Burditt

dB permissions were good -- i've done all that before. Got it fixed and
you were right; it was to do with the hash algorithm changeover in
4.11. My prod. server had the system var old_passwords=On but not my local.

So anyone else who runs into this: it's not enough that both
installations use 4.1.11 (or .12 or whatev) -- use SHOW VARIABLES like
'old_%' to see that setting.
 >> Stay informed about: exporting tables with password fields