feat!: change the code to support postgresql instead of sqlite #274
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.
Hello,
These are some modifications to run the application with postgresql.
I changed some column size to be able to restore the dump of sqlite in postgresql.
I changed some test because postgresql take care of primary keys, however, I didn't finished this job, and some more tests will need changes if you want to run these with postgresql.
In my opinion, you can keep sqlite for test.
related: #267