Errors upgrading from 0.12 to 0.20
Hello,
I updated the docker from 0.12 to 0.20 using
docker-compose up --build -d
I have some errors in the logs (attached), but it seems to work.12 Replies
I saw that I have to migrade DB using those commands:
I launched a
yarn database:migrate:prod and I have no error.
Then I launched yarn command:prod workspace:sync-metadata -w 7823fcc0-feff-4ae5-8555-86c42cf82b6c -f and I have many errors (attached) starting with:
Error executing migration QueryFailedError: type "workspace_741y2bhupr008ai8qozyb7f58.messageChannel_syncStatus_enum" does not existI think you might have some legacy errors from 0.3.3. Could you make sure that your enum is named: messageChannel_syncStatus_enum and not messageChannel_syncstatus_enum ?
Bonjour @charles
Indeed, it seems to be the first one.
How do I update this?
you can just rename it using an SQL query:
ALTER TYPE workspace_153t7qnxistacfxobsx8zmpy8."messageChannel_syncstatus_enum" RENAME TO "messageChannel_syncStatus_enum";Thanks @charles
All good, now the second command works. I only have two warnings:
The second one is a bit worrying. Do you see the calendarEvent table in your workspace schema?
Yes this one?
It seems the table exists now (just created with the following commands?):
So I relaunched
yarn command:prod workspace:sync-metadata -w $workspaceId -f and now I only have:
yarn command:prod migrate-0.20:update-message-channel-sync-status-enum
When I try this command, I get:
Ok, looks better!
sorry there is a mistake in the command: you should add the -w option to these commands
otherwise it tries to sync all workspaces and I suspect you have a legacy demo workspace in your database (you can just delete it btw + delete all data tied to its workspaceId in metadata and core schema)
Seems all good. Thanks @charles
Très bonne journée à toi 🙂