Moving through the update chain from 0.34.0 to 0.35.0 >
Hey All, I'm starting to start the chore up upgrading through the chain of releases. At the moment, I'm running into another migrations issue. I wish there was a core migrations checker/sync. It seems from time to time a migration is missed and it totally nukes the entire app.
Anyways, upon the upgrade command I see this failed query:
`
At the moment, I don't see any other errors. The app just hangs. Any ideas whats going on here?
4 Replies
Hello @Raph, unless I'm mistaken you've shared partial log ?
Since 0.44 upgrade experience has evolved and now upgrading a workspace should be easier, as now each workspace is versioned and the upgrade command won't run if does not implies an expected upgrade gap
We've also planned to implem a tool that will handle incremental upgrade on its own one by one
Any suggestions and remarks are welcomed
Hey @prastoin yes - upgrading from one version to the next is a total drag. I've been putting it off since we're stable, but I'd like to take advantage of some of the new features. Is there database health check command?
From my digging it seems like I'm missing a field/column and an ENUM. I'm just trying to track down which version it was missed in.
The other thing I think would be helpful would be variable examples for each new environment variable that is introduced. Ok, great there is a new ENV Var, what are the options? (:
Hello @Raph
Is there database health check command?The upgrade command kinda serve this role, as said above starting from
0.44 workspaces migrations are versioned directly in base. So corrupting a workspace should not be possible on "invalid" upgrades anymore
From my digging it seems like I'm missing a field/column and an ENUM. I'm just trying to track down which version it was missed in.This should be fixed by the corresponding version `yarn database:migrate:prod"
Ok, great there is a new ENV Var, what are the options?Rodger ! Do no hesitate raising an issue or pullrequest on the related documentation This seems to be due to an un-authenticated request, please try re-logging in