MySQL Connection - Problem Solved + Additional Info
asg618 at mac.com
Mon Aug 1 22:52:23 CDT 2005
Ken's solution worked like a charm and I'm back to work!
For those interested, I did some research on the background of this problem,
and the explanation is provided in the MySQL online manual, starting here:
With explanation of the workarounds here:
One potential problem pointed out is that OLD_PASSWORD() may one day be
deprecated. Hopefully by then most affected third-party clients, like Rev,
will have upgraded to a client library that supports the new authentication
Golub & Isabel, P.C.
On 8/1/05 10:25 PM, "Ken Ray" <kray at sonsothunder.com> wrote:
> On 8/1/05 3:25 PM, "Alan Golub" <asg618 at mac.com> wrote:
>> On 8/1/05 4:00 PM, "Ken Ray" <kray at sonsothunder.com> wrote:
>>> Yes, we ran into this just recently. You need to change the password that is
>>> stored in the DB to the "old" (pre-4.1) format for compatiblity with
>>> everybody. This is the syntax at the mysql prompt (using "tempUser" as the
>>> user name, "localhost" as the host, and "mypass" for the password):
>>> set password for "tempUser"@"localhost"=OLD_PASSWORD("mypass");
>> I'll need to wait until tonight to run this solution from home, but I just
>> want to make sure I 'get it.'
>> Ok, so for each user accessing the 4.1 or later database, changing/setting
>> the password via the OLD_PASSWORD() function stores the password in a manner
>> compliant with post-4.0 versions of the server, thus allowing seamless
>> (hopefully) access to the db from Rev?
> Yup! You got it!
>> Thanks, Ken!
> No problem...
> Ken Ray
> Sons of Thunder Software
> Web site: http://www.sonsothunder.com/
> Email: kray at sonsothunder.com
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
More information about the use-livecode