-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MariaDB: Add log message for versions < 10.5.10 with broken table name resolution MDEV-25362 #1544
Comments
Thanks for reporting this!
|
I use MariaDB, the schema is from the stable version (current), and I used the stable version only so far. |
Ok, so when I install the stable version and then upgrade, I should see the same error? |
I hope so |
when I installed the stable, in Docker hub it seemed stable was from 4months ago. |
I'll try... can you test this too? |
Test a fresh reinstall? Basically my install is from last weekend when I wanted to test photoprism stable, and migration to preview was from this morning. |
Yes, just to be sure. Sounds like schema migrations didn't run (they should every time photoprism starts). The |
Does it work when you enable experimental features (advanced settings or in docker-compose.yml) and then restart? |
It was already enabled (I enabled it when on stable), and at start I only have this in the logs:
|
I still have the error when importing after a restart:
|
I assume you're using version 10.5 of MariaDB with the same settings as shown in our docker-compose.yml example? |
I use |
So this release? https://mariadb.com/kb/en/mariadb-10148-release-notes/ We haven't tested it as it's not a supported version anymore: https://endoflife.date/mariadb I'll try to figure out what the issue with this version is then... |
From my understanding, the following features might be missing in 10.1 for our thumbnail update query to work: https://mariadb.com/kb/en/mariadb-1032-release-notes/#notable-changes |
ok, will try to update my system mariadb to 10.5, migrating my other services. |
I have been having the same issues with 10.5, so it's probably unrelated. |
ok thanks for the feedback :) |
PhtoPrism will now show more helpful error messages in case somebody is using a deprecated database server. I've also added docker-compose config files for older versions of PhtoPrism, MariaDB, and MySQL for testing. |
We're using 10.5 for development and never saw this. I've just tested all versions down to 10.1 and it only happend with 10.1, even 10.2 was working. How can we reproduce the issue? |
I've been seeing this on the
|
Now with the latest changes, I get the misleading error message:
|
See community chat. Seems the issues are gone when upgrading from 10.5.x to 10.5.12, so may be a MariaDB bug as MySQL is working great. I started reading the bug list to figure out details, but it's too long. |
Looks like this is an official MariaDB bug: |
The error message is now:
Acceptable? |
Also fixes issues with older versions of MariaDB, see #1544
After updating to preview from stable version, I get these errors:
How could I fix them?
Thanks for your help, and your very great project.
The text was updated successfully, but these errors were encountered: