Hello, @XOJO, is there anyone that could point a documentation or an official document where it states the functional versions of xojo for each version of MariaDB ? apparently there are a lot of issues connecting to MariaDB on linux servers on the latest public XOJO version .
I see on the tracker feature requests to replace MySQL with MariaDB 8 years ago, so sad
it simply does not connect, i have it on a Debian 11, and MariaDB 10.8, and running it from MacOS works smooth, running that from Debien does not work, and seeing the trackers on XOJO bugs William said āFixed on MacOS, Windows but not on Linuxā so i assume there is my issue
Any other code that i run connects without any issues, but not any xojo app.
i simply get Server error : Access denied for user āuserā@ā127.0.0.1ā (using password: YES) but never get such error for same code but on MacOS running ssh Tunnel , so Password is ok, code is ok OS seems to be. the problem or at least the running part on Linux
well user is out of the question, apparently there is something between the servers , on the socket part i fix it by adding
[client]
socket = /run/mysqld/mysqld.sock
to 50-client.cnf
then doing a ln -s /run/mysqld/mysqld.sock /tmp/mysql.sock and that fixed the issue locally, however it seems that under no circumstances does not want to work via tunnel from the other Debian machine . It does work from MacOS so that is the weird part . Both servers are identical and have same dependencies
Well thatās the funny and confusing part, as same username and password works on any other code, it does work locally now on the server which has Mariadb installed but it does not work when called via tunnel or via remote. So how that could be an authentication issue ? is it related to XOJO ? as any other code just works , including XOJO on local
The combination of user@origin must be allowed, if peter@123.1.1.1 gets access, it does not mean that peter@127.0.0.1 will, if some restriction is set.
Read servers docs about the subject tracking the issue.
iām not sure i get it, as said same user ,
same connection works on shell,
works on xojo when app runs locally,
works on shell when run over the tunnel,
does not work on xojo when run via tunnel on the second debian server,
but it does work on MacOS via tunnel same code same connection parameters
so Yes fsStat@127.0.0.1 does work on any steps i enumerated earlier, except on the app when the app is on the second debian server which should allow same functionality .
why not ? what is the purpose of the Tunnel ? as for what i know is forwarding and mapping the original port to a new port and mapping it as local, so same functionality should be applied