Skip to content

migration to another DB backend #3336#3343

Open
mkf-sysangels wants to merge 10 commits intobunkerity:devfrom
mkf-sysangels:migration-to-another-DB-backend-#3336
Open

migration to another DB backend #3336#3343
mkf-sysangels wants to merge 10 commits intobunkerity:devfrom
mkf-sysangels:migration-to-another-DB-backend-#3336

Conversation

@mkf-sysangels
Copy link

migration to another DB backend #3336

this PR has several other dependencies that will be published in separate PRs. Current state is ALPHA until the dependencies will be fixed.

@mkf-sysangels mkf-sysangels marked this pull request as draft March 17, 2026 10:50
Quoted env file values cause database connection failure
@TheophileDiot
Copy link
Member

Hi @mkf-sysangels, great idea. I’d prefer each P/R to be small, atomic, and independent, without depending on other open P/Rs, since GitHub recommends “small, focused pull requests that fulfill a single purpose” because they’re easier to review and merge.

source: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/getting-started/helping-others-review-your-changes

@mkf-sysangels
Copy link
Author

Hi @TheophileDiot

thank you for the information.

As the initial version is still alpha i need first fix issues to make it working on all scenarios.

First migration SQLLite > mysql-cluster was successful

Currently fixing mysql > postgresql patroni cluster

As soon as i have full cycle i will call it beta so others can test it too.

- fix postgres connection on patroni configuration (postgresql cluster)
- fix SSL connect error on wrong selected root CA PEM
- fetch root CA when cert is issued by trusted CA
- add timeouts
- add PID file
- add debug logging
- compare TLS conections for differences
- abort on critical certificate error
- fix TUI scrolling and size changes
- fix ssl connection issue
- add --auto-switch for instant migration
fix errors on migration to SQLLite
@mkf-sysangels mkf-sysangels marked this pull request as ready for review March 18, 2026 17:08
@mkf-sysangels
Copy link
Author

I successfully migrated:

SQLLite > mysql > postgrsql > mysql > SQLLite

Ready for public review

Status:
BETA until we have enough test-cases

…ces are not re-synced afterward in the migration utility.

data rows are imported with explicit id values, but sequences are not re-synced afterward in the migration utility.

adding an automatic sequence reset step right after import so next inserts use MAX(id)+1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants