Does mySQL plugin stopped working for older Xojo versions?

Databases
1

I have a private app online, last modified with Xojo 2019R3.
Today I was going to make some changes but and opened it with 2024 r2.1. However there were so many events and other things being deprecated (and had a lot of compiler errors) that I decided to just edit it with the old Xojo 2019R3.
It compiles and starts correctly with the old code, but to my surprise, in my windows 11 machine, when running the app it won’t connect to my local Mysql database (development machine has Wamp).
Tested Xojo 2024r2.1 and it connects successfully. Back to Xojo 2029r3 it fails, on the same machine.
Am just guessing that probably the mySQL community plugin just does not work in the older Xojo version.
Does anyone know about this? MySQL version is 8.0.27, and it won’t help to put an older Mysql version, because the online app has that Mysql version too.

2

At some point the connection technology probably changed, probably at some point in those 5 years. If you intend to use new DB tech, you probably will need to put some effort to upgrade your app or downgrade the DB to an older version.

3

Yes, contrary to your assumption, we did put some effort. The production app was upgraded to a different architecture (Delphi +TMS Web Core / Rest web services) two years ago and follows a better maintenance path.
I kept the Xojo application live for pure nostalgia, for going back to what I did to implement some things, and to practice future changes. I still like Xojo for rapid prototyping and other stuff like Arm 32/64 SBCs applications, and the fact that it compiles for all platforms from any one of them.

Anyway, you missed the point of my question, which is to know if Xojo 2019.R3 has support for newer ( >=8 ) MySQL versions.
At this time I can answer myself instead of guessing. It does work with older MySql versions, not with MySql 8 on WAMP. It also works with MariaDB 10.6.

4

MySQL 8 comes with two different password encryptions, Standard and Legacy.

You will certainly need to create a new user using the legacy password to work with Xojo 2019

CREATE USER ‘username’@‘localhost’ IDENTIFIED WITH mysql_native_password BY ‘password’;
4 Likes
5

Actually, you are not figuring it, you are using the knowledge provided.

6

there was the same problem of password encryption change with postgres
moving from xojo 2019 to 2023 I had to change some code to take that into account
mysql is probably the same as Jeremy said above.

7

MySQL 8, introduced the encryption algorithm to a SHA-256 authentication using cache known as option caching_sha2_password. MySQL 8.4 enforced it. The legacy mode is deprecated and will vanish at some point.

Jeremie is correct, but you may not need to create a new user, just downgrade the current one to the old authentication scheme like

ALTER USER 'username'@'whateverhost' IDENTIFIED WITH mysql_native_password BY 'my password as always';
FLUSH PRIVILEGES;

8

Thanks Jeremy, will take that into account, although is is more likely we will use the current Xojo version for future projects.

9

If you say so …