We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Now that we routinely offer a sql/psql/new-version/old-version-precheck.sql perhaps omego could support doing a precheck.
sql/psql/new-version/old-version-precheck.sql
The text was updated successfully, but these errors were encountered:
Is *-precheck.sql guaranteed to be read-only, now and in future?
*-precheck.sql
Sorry, something went wrong.
Logically, I'd say yes, but we should document this. For me, this is a process of adding "API" to the sql/ directory.
sql/
Agreed. I plan to always end it with ROLLBACK;. At very worst we may consider recording in dbpatch that it was run.
ROLLBACK;
dbpatch
No branches or pull requests
Now that we routinely offer a
sql/psql/new-version/old-version-precheck.sql
perhaps omego could support doing a precheck.The text was updated successfully, but these errors were encountered: