-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
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
Create documentation for submitting a data-migration #930
Labels
Comments
Related to: #959 |
3 tasks
3 tasks
michplunkett
added a commit
that referenced
this issue
Jul 18, 2023
## Fixes issue #930 ## Description of Changes Add documentation to make data-migrations a more transparent process. ## Tests and linting - [x] This branch is up-to-date with the `develop` branch. - [x] `pytest` passes on my local development environment. - [x] `pre-commit` passes on my local development environment.
Merged
3 tasks
sea-kelp
pushed a commit
to OrcaCollective/OpenOversight
that referenced
this issue
Sep 24, 2023
lucyparsons#930 Add documentation to make data-migrations a more transparent process. - [x] This branch is up-to-date with the `develop` branch. - [x] `pytest` passes on my local development environment. - [x] `pre-commit` passes on my local development environment.
sea-kelp
pushed a commit
to OrcaCollective/OpenOversight
that referenced
this issue
Sep 25, 2023
lucyparsons#930 Add documentation to make data-migrations a more transparent process. - [x] This branch is up-to-date with the `develop` branch. - [x] `pytest` passes on my local development environment. - [x] `pre-commit` passes on my local development environment.
AetherUnbound
pushed a commit
to OrcaCollective/OpenOversight
that referenced
this issue
Oct 9, 2023
lucyparsons#930 Add documentation to make data-migrations a more transparent process. - [x] This branch is up-to-date with the `develop` branch. - [x] `pytest` passes on my local development environment. - [x] `pre-commit` passes on my local development environment.
AetherUnbound
pushed a commit
to OrcaCollective/OpenOversight
that referenced
this issue
Oct 9, 2023
lucyparsons#930 Add documentation to make data-migrations a more transparent process. - [x] This branch is up-to-date with the `develop` branch. - [x] `pytest` passes on my local development environment. - [x] `pre-commit` passes on my local development environment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What's the issue?
The data-migration process uses the Alembic framework. Currently, we don't have any local documentation on how to quickly do a data-migration. Our data-migration files are also named in a way that does not at all indicate the order in which they were created. This can be addressed by adding an epoch timestamp to the front of the file upon its creation: Link
The text was updated successfully, but these errors were encountered: