Uh oh!
There was an error while loading. Please reload this page.
This repository was archived by the owner on Jun 7, 2023. It is now read-only.
Alembic / migration - #48
Merged
Merged
Conversation
bjones1
marked this pull request as ready for review
June 18, 2021 15:26
bjones1
commented
Jun 18, 2021
CollaboratorAuthor
I've written all the migration my database needs (minus a few pending questions); @bnmnetp, try this on your test server and see what it reports. |
bjones1
commented
Jun 25, 2021
CollaboratorAuthor
This needs RunestoneInteractive/RunestoneComponents#1213 to be merged in order to pass. |
Add: SQL fixes for violations.
bjones1
commented
Jul 21, 2021
CollaboratorAuthor
@bnmnetp, this is rebased to fix merge conflicts and ready to review. |
bjones1
commented
Jul 27, 2021
CollaboratorAuthor
@bnmnetp, pinging... |
This file contains hidden or 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
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 WIP shows progress toward migrating PostgreSQL from web2py to the BookServer. Notes:
rename_indices.sql. It also includes the beginning of fixing NULL records where the new constraints specify NOT NULL.alembic revision -m "testing" --autogenerate), the resulting Python file has a LOT ofdrop_indexstatements. What do you see for your DB? Do we need to add more indices to the BookServer, or is what we have OK?