Back to my initial problem. It is that "localhost" and "127.0.0.1" are not the same for the mysql.user table.
And (dunno why), on this new server, when I try to connect to "localhost" with the user "user", it is converted to firstname.lastname@example.org and this host "127.0.0.1" is not in the mysql.user host column. There is only "localhost" values. So the quick solution is to copy the "locahost" mysql.user entry with a host value of "127.0.0.1" and the connexion works.
But if I edit the user (there are managed by PLESK), all entries for it are removed and only the "localhost" one is put back. Do it again man.
So now the question : why is this "localhost" be converted to "127.0.0.1" in between rebol and mysql. On the pretty same server I had before it does not do that.
If it's on Linux servers, try comparing the /etc/hosts files content.
Using on1 Photo RAW beta right now, talked to devs, they claim to use LevekDB from Google, claiming it is faster than SQLite (though highly unreliable and not prone to failures). However, reading Wikipedia articles, I found out about Lightning DB - seems nice: https://en.wikipedia.org/wiki/Lightning_Memory-Mapped_Database
I remember reading about it some time back. The licensing notes are interesting. Another example of people being surprised at how well simplicity works.
It would be interesting to port to Red, maybe first as a wrapper, then a fresh implementation in Red/System. So many DB choices these days.
Is SQL Lite usable on REBOL3 ?
I think Kaj has a SQLite wrapper and it is stable though I didn't use it.
Have you a link for it ?
Sorry, I don't have. Actually not sure if it was for Red or R3.
It is not supposed to replace SQLite3, it's more a different project ....
When the bounty for ODBC red will be rewarderd another one will start for SQLLite 4
Pekr: As I understand SQLite4 is not *just* a key/value database, "SQLite4 is a complete, relational, transactional, ACID, SQL database database engine ". That key/alue is just one of its stored engines. So it actually is a new version of SQLite3 which is not backward compatible, but also not a replacement. Thanks for sharing the link by the way.
And it uses its key/value storage engine for all indexes in all tables in a database which is different than sqlite3.