Open maknapp opened 3 years ago
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:
ALTER TABLE "cr_seo_sitemap" RENAME CONSTRAINT "cr_seo_sitemap_group_check" TO "seo_sitemap_group_check"
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_TABLEPREFIX environment variable is set to `cr`. Should the migration check for that?Steps to reproduce
Additional info