-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
3.7.1 migration error #354
Comments
Same error over here coming from 3.6.3 to 3.7.1 but using MariaDB 10.3, and also have a table prefix in place and have verified the migration works if there is no prefix. |
Same error for me. Anyone figure this out? |
This was some time ago, but I believe I renamed the constraint to remove the prefix so that the migration had something to do. Something like this for postgresql: And then run the update again. |
@maknapp Didn't work for me, but thank you! |
Description
I am using PostgreSQL and I am getting a migration error when updating from 3.6.7 to 3.7.1.
I checked that table and there is a constraint with a similar name:
cr_seo_sitemap_group_check
. My DB_TABLE_PREFIX environment variable is set tocr_
. Should the migration check for that?Steps to reproduce
Additional info
The text was updated successfully, but these errors were encountered: