Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use database Migrations #9

Closed
infinity-plus opened this issue Jan 12, 2023 · 1 comment · Fixed by #12
Closed

Use database Migrations #9

infinity-plus opened this issue Jan 12, 2023 · 1 comment · Fixed by #12
Assignees
@infinity-plus
Labels
enhancement New feature or request

Comments

@infinity-plus
Copy link
Contributor

Current database interacting functions do not handle schema changes and make the app crash when there is a difference in already existing schema and source code schema.

I plan to use rusqlite for database migrations as it is safe, easy to use, convinient and better performing.
Current database code needs to be refractored for using rusqlite.
@infinity-plus infinity-plus self-assigned this Jan 12, 2023
@infinity-plus infinity-plus added the enhancement New feature or request label Jan 12, 2023
@infinity-plus
Copy link
Contributor Author

Ended up using rusqlite_migration = "1.0.1"

@infinity-plus infinity-plus mentioned this issue Jan 13, 2023
Merged
@infinity-plus infinity-plus linked a pull request Jan 13, 2023 that will close this issue
Use Database Migrations to handle schema updates #12
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@infinity-plus infinity-plus

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use Database Migrations to handle schema updates ProjectBlackPearl/project_black_pearl
1 participant
@infinity-plus