Conversation
Earlier work was done on the `initial-prototype` branch and has only been slightly cleaned up for this release. Documentation, CI (GitHub Actions), dependency monitoring (Dependabot) and a host of other TODO items have not been completed as of this specific commit. Additionally, confirmed bugs such as GH-20 remain and should be fixed before the first v0.1.0 release. Some test files from the WhyAskWhy/mysql2sqlite-dev project are included in this commit. I am authorized to include them as well as use the project name. This commit provides two (mostly) working binaries: - `mysql2sqlite` - main binary to sync a MySQL database to a SQLite database - `check_mysql2sqlite` - Nagios plugin to validate source MySQL database against generated SQLite database As already noted, much, much work remains to polish and refactor this code. Even so, I am already using it in limited production use in order to help shape development efforts. Already this has proven useful in abandoning the plan to use Write-Ahead Logging (`WAL`) mode when interacting with the SQL database and instead use classic `DELETE` mode instead (compatibility). refs GH-19
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This commit provides two (mostly) working binaries:
mysql2sqlitecheck_mysql2sqliteWorth emphasizing
Some test files from the
WhyAskWhy/mysql2sqlite-devproject are included in this commit. I am authorized to include them as well as use the project name.Known issues
Earlier work was done on the
initial-prototypebranch and has only been slightly cleaned up for this release.Documentation, CI (GitHub Actions), dependency monitoring (Dependabot) and a host of other TODO items have not been completed as of this specific commit.
Additionally, confirmed bugs such as GH-20 remain and should be fixed before the first v0.1.0 release.
Much work remains to polish and refactor this code. Even so, I am already using it in limited production use in order to help shape development efforts. Already this has proven useful in abandoning the plan to use Write-Ahead Logging (
WAL) mode when interacting with the SQL database and instead use classicDELETEmode instead (compatibility).References
fixes Merge initial prototype codebase after minor cleanup effort #19
https://github.com/WhyAskWhy/mysql2sqlite-dev
https://github.com/WhyAskWhy/mysql2sqlite
https://github.com/go-sql-driver/mysql
https://github.com/mattn/go-sqlite3
https://github.com/joho/sqltocsv