World: r3wp

looks like mysql-admin doesn't use PASSWORD() to create passwords

that's the problem

works when I set it with PASSWORD()

hope that helps a bit

Sure it helps, thanks!

I'll try to release an updated version this weekend that fix such 
case.

excellent

dumb question.. is this a valid query?

select i1.id,i1.ip,i1.session from isa i1,isa i2 where i1.ip=i2.ip 
and i1.session<>i2.session order by i1.ip
about 70'000 records in isa
running this query seams to crash/block the mysql server..

not a well constructed query. unless my mental parser isn't working. 
You are asking for each and every row where it doesn't match the 
current row... now I don't think that is your true intent ...

that would be something like 70,000 * 70,000 results

valid but not like useful , (or likely to finish soon)

stating what you actually want to accomplish could help

Henrik: Can yo give me the mysqladmin command line you're using to 
create a new user ?

mysql-admin is a GUI client.

I'll see if I can find some docs on it. it's the client you can download 
from mysql.com

Ok, so you mean MySQL Administrator (and not the mysqladmin.exe command 
line tool).

it's called "mysql-admin" under linux. looks like your name is correct.

http://dev.mysql.com/downloads/administrator/1.1.html<--- that one

Tried creating a user using that tool under WinXP and OSX, then I 
tried connecting with mysql-protocol.r => no problem...

if you look in your user table, what length is the encrypted password?

*63D85DCA15EAFFC58C908FD2FAE50CCBC60C4EA2

ok, mine are only about 16 chars long

so it's simply a different encryption scheme for some reason

when I created it from the console, I got a properly encrypted password 
like yours

16 chars are old passwords IIRC

I think the client is confused about that. The error log for it says 
that old passwords are not supported for 5.0. I initially tried to 
turn old passwords on, because I didn't think mysql-protocol.r supported 
newer ones.

then I tried to turn them off again through the GUI and it didn't 
change.

Could you activate : trace/net on before using mysql:// and show 
me here the server information retrieved by the driver.

that'll take a short while, the PC that the mysql server is on has 
been taken down. :-)

Ok, I see...no problem, just post it here when you'll have the log.

setting it up now (need to do it anyway)

imo it is like this - when you have db created with old scheme, db 
will not automatically rebuild it for you using new method ...

it is stated somewhere in docs iirc, you have to rebuild it .... 
the thing is, that length of old-password field is limited or something 
like that ...

pekr, would it work the other way around as well? I thought it was 
only initial authentication that was different.

install from scratch

I didn't do that, so it must have been done with new passwords. I 
could immediately overwrite the old style password with the new style 
and it worked immediately

not sure, not having enough experience, just stating what I remember 
about it ...

ok then ...

another thing I experienced: The server was moved to a new location. 
For some reason, everything went FUBAR, because DNS had not been 
set up. This caused connecting to the server to take about 60 seconds 
to get through. When I looked in the list of connections, it just 
says "logging in" for that long time. I connect to the server with 
an IP address, not a host name, so what's going on?

not sure what is causing the lag. You would need to look at low level 
communication - inspecting packets in something as ethereal ...

or looking at mysql logs, if there is not something suspicious ...

when the server is connected, everything runs at full speed

The server may try a reverse dns request on your IP when you connect 
and ends with a timeout after 60secs.

could be that, it connects just fine now here at home

could be that <period> :-)

Good news : I've finally reached a very stable version of the mysql 
driver with v5+ servers ! The stability garanted only if using a 
database created with a v5+ server, copying old 3.x files in v5 server 
works but results in a big mess and unstable behaviour. Exporting/Importing 
v3.x data in v5 server using SQL flat files works very well (except 
for user with passwords, better recreate them in v5 directly).

copying old 3.x files in v5 server works but results in a big mess 
and unstable behaviour
 <--- is that because of MySQL or mysql-protocol.r?

MySQL, even MySQL Admin tool get lost when acting like that.

I mean running a v5 server with v3.x tables.

I've found numerous bugs in mysql-admin. I think this tool is not 
particularly trustworthy