World: r3wp

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

I've just run a big stress test with 40'000+ requests generating 
around 2Gb of traffic without any trouble ! No bad handshakes anymore 
if you're using v5+ tables and new passwords.

I'm testing it over an ADSL connection now against a V5 server with 
multiple users. no trouble at all.

I've just uploaded v1.06 which adds support for a few missing new 
datatypes.

http://softinnov.org/tmp/mysql-protocol.r

downloading.., thank you!

Thanks!

BTW, an old question I continue to ask but how do you all handle 
checking whether a port is open or not?

This should work: either insert db-port [ping] [print "port opened"][print 
"port closed"]

If it is at reading data : try [copy db-port] should work too.

there are times when the connection to the database won't wake up 
after hours of sleep and the application locks. this also happens 
with mysql-admin, but I wonder if it really is server or a client 
side problem.

My driver should reconnect automatically is the connection is closed 
by the server when you send a new request even after hours of sleeping. 
I need to test that with a v5 server to see if it behaves as expected.

Thank you. With the old protocol I would sometimes get  an error 
 (and exit from the program) when I inserted into a closed port. 
I will give these a shot.

I can see that mysql console has no problem in reconnecting where 
rebol and mysql-admin fail

Doing the following test works for me (v5 server) :

1) Load the REBOL mysql console : do %mysql.r
2) Connect to the server
3) Command: show tables
4) result ok
5) Stop/Start the server
6) Command: show tables
7) result ok (the driver has reconnected transparently)

Erratum: replace the step : do %mysql.r by :

do %mysql-protocol.r
do %mysql-client.r
mysql

Doc, any news on when will you go v1.0 with the postgress driver?

Great Doc!
I didn't believe you'd ever call a version worthy of 1.0 ;-)

It takes, at least, 4 for years of beta-testing to become 1.0 ;-))

and intense bugfixing sessions 4 days before releasing 1.0 :-)

Postgresql: Don't know, I may work on it this summer for a customer, 
so I may release new versions. I didn't had much feedback on this 
product, maybe too few users in the REBOL community...?