You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a few custom plugins, and havent had issues when I upgraded from 4.1.11 to 4.2.9, but when I did the upgrade to 4.3.2, I got an error message on the PostgreSQL DB saying that there's a duplicate column, but I have an empty DB. The specific error is
psycopg.errors.DuplicateColimns: column of relation already exists..."
But I thought I cleaned the DB and the migration. Is there a way to force the DB to clean as this same code worked well and fine on another system I used.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have a few custom plugins, and havent had issues when I upgraded from 4.1.11 to 4.2.9, but when I did the upgrade to 4.3.2, I got an error message on the PostgreSQL DB saying that there's a duplicate column, but I have an empty DB. The specific error is
psycopg.errors.DuplicateColimns: column of relation already exists..."
But I thought I cleaned the DB and the migration. Is there a way to force the DB to clean as this same code worked well and fine on another system I used.
Beta Was this translation helpful? Give feedback.
All reactions