forcibly release all locks active at the time of migration [MARXAN-1091] #853
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is so we don't risk running into a constraint violation when adding a FK reference later in the migration. There should really be no "active" users by the time this migration runs, as there is no production environment yet, and LOFU should help the few developers and test users to keep their sessions running smoothly nevertheless. I am not sure how wise it is to use an Unicode emoji in a PostgreSQL comment, but apparently we'll be fine with this 😇.
|
This pull request is being automatically deployed with Vercel (learn more). marxan – ./app🔍 Inspect: https://vercel.com/vizzuality1/marxan/BfG2dugJJrv6voXPysEtPm31vjPw marxan-storybook – ./app🔍 Inspect: https://vercel.com/vizzuality1/marxan-storybook/CZZLe3StFmXTcppR4HMdbg1Dns8A |
rubvalave
approved these changes
Feb 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is so we don't risk running into a constraint violation when adding a FK reference later in the migration.
There should really be no "active" users by the time this migration runs, as there is no production environment yet, and LOFU should help the few developers and test users to keep their sessions running smoothly nevertheless.
I am not sure how wise it is to use an Unicode emoji in a PostgreSQL comment, but apparently we'll be fine with this 😇.