Open CarlSinclair opened 2 months ago
What is you MariaDB version. Also there is a lot of chances that your distro is enforcing some behavior, I cannot test them against the multiple MySQL/MariaDB flags that exists, do check your error on Stackoverflow and see if there's a specific config on your side to change in your database config.
Ver 15.1 Distrib 10.11.7-MariaDB, for Linux (x86_64) using EditLine wrapper
Pretty weird that this happened on a fresh install though, following the instructions.
Hello, got any news regarding that issue ?
What info do you need? I provided the MariaDB version.
As I was saying above, I'm not planning to test Movim on the myriad of MySQL/MariaDB flavors, but I'm open to integrate fixes that you may find along the way.
I tried setting it up using Postgres but ran into other problems probably due to the fact that I'm on RHEL, so I'm just going to give up on it for now until I set up a Debian-based machine.
I am seeing the same issue, on a fresh Debian 12 installation, MariaDB info: Server version: 10.11.6-MariaDB-0+deb12u1 Debian 12 Movim is the only database that was created, and no modifications to any MariaDB configs.
I am seeing the same issue, on a fresh Debian 12 installation, MariaDB info: Server version: 10.11.6-MariaDB-0+deb12u1 Debian 12 Movim is the only database that was created, and no modifications to any MariaDB configs.
Perhaps this is related: https://jira.mariadb.org/browse/MDEV-31987?jql=text%20~%20%22set_foreign_key_Check%22
Did you find the cause of the issue ?
There was an update to mariaDB regarding the handling of foreign keys. I managed to install MariaDB 10.3 using this: https://olvy.net/blog/olvy-ported-mariadb103-to-debian12-and-ubuntu2204/
If I understood correctly, the update was first released as a patch, but I did not figure out when it was pulled into the normal releases.