-
Notifications
You must be signed in to change notification settings - Fork 1
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
Command to migrate MariaDB database #61
Conversation
For data validation summary with these scripts (see #60), can we print row counts, etc. as tables to improve readability (maybe using the |
* main: (158 commits) Got rid of unnecessary spacing changes Centralized GRANTs in a single post-update hook New subsystem and hook function that updates permissions after all schema updates Removed some old commands that may not be useful anymore Updated JetBrains files Update and include new tables Update and include new tables Started upgrading macrostrat migration scripts Updated Macrostrat subsystem definitions Moved 'column-builder' views into new subsystem architecture Started re-working v2-transition code into various places Move sql alteration functions to database-upgrades directory Remove dependencies on local packages in pyproject.toml Update README.md Storage scheme migration Updated storage migrations Updated maps migrations Create some explicit migrations Remove unused function Improved organization of paleogeography sub-app ...
…e all data exists before migration in dev
…ostrat into maria-migrae
… mode parameters for pgloader command to work
Changes to MariaDB migration to integrate with Macrostrat CLI
…mariadb-migrate-postgres step
…d macrostrat_temp
…and kep the schlep scripts for the tables that are modified in the pre/post migratino scripts.
Removed v1 schlep scripts and moved all index files here schlep-index. These changes are referenced from #81 |
This branch contains migration code that enables a complete MariaDB to PostgreSQL database migration, as detailed in #60. The script in this pull request should make several key data evolutions:
macrostrat
MariaDB database to PostgreSQL, retaining all database tables, rows, etc.macrostrat_two
, currently) into Macrostrat's PostgreSQL database/macrostrat
schema, overwriting tables if neededmaps
tomacrostrat
#80:Regenerate foreign keys from other schemas (e.g.,This has been moved to future work, based on some complexities identified by @mwestphall.maps
) as needed.A successful operation of this script will result in full integration of all data from MariaDB, allowing the Macrostrat API to operate off of a single PostgreSQL database (UW-Macrostrat/macrostrat-api#229)
Architecturally, this should be implemented within the
macrostrat
command-line application:macrostrat
subcommand, e.g.,macrostrat migrate-mariadb
(we can figure out the "right" name later)macrostrat.toml
rather than replicating them elsewheremacrostrat.database
module for running SQL commandsmacrostrat v1 schlep
scripts that were the initial version of this processLatest update:
compare_data_counts()
to compare any two databases passed through as parameters.Next steps: