-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Error running migration ...postgres_relationships_v2_v3 relation "payload_locked_documents" does not exist. #10162
Comments
Please add a reproduction in order for us to be able to investigate. Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided. Why was this issue marked with the
|
I am creating migration like this: If this is not the way please let me know and I will try to re-run. |
After manually creating missing tables like so:
Another error:
Looks like migration script attempts to read the new column name instead of the old one |
This allowed the migration to run. Server runs in production mode fine. Starting in dev mode detects some sort of schema mismatch and crashes. I can recreate dev DB I guess, not that important, still not very clean.
|
Disabled locking on all collections removed the need for hacky |
That error indeed existed, but in 3.10.0 it was resolved #10080 I just tested again, here's the repo - https://github.com/r1tsuu/payload-2x-3x-migration-test which has migrations from v2 and seeds some relations in migrations, the migration on 3.12.0 passes successfully, while on 3.9.0 I have the same error with |
Nope migration was starting and failing mid-run until I've put I managed to run my migration in 2 steps. Step 1: alter column names from camel to snake case myself
Step 2: migrate data missed by automatic migration (obfuscated so you can make sense of it):
|
Describe the Bug
Attempting to migrate an existing v2 DB to v3 format is not as smooth as it could be.
headingFontFamily › heading_font_family
, but this is easy to check programmatically and very error prone otherwiserelation \"payload_locked_documents\" does not exist
Link to the code that reproduces this issue
No link but see a dump attached
Reproduction Steps
bldry_staging
and make userbldry
owner/give permissionsZipped tar file, because GitHub: bldry.tar.zip
Schema: 20241214_162106_imprintLinks.json.zip
Which area(s) are affected? (Select all that apply)
db-postgres
Environment Info
The text was updated successfully, but these errors were encountered: