-
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
Migrate database to GORM and new schema #8
Conversation
d79b75b
to
a4e62e8
Compare
a4e62e8
to
2cf6e37
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some questions and comments. Haven't had the time to review the tests yet.
6b8c45a
to
7843bfb
Compare
f2d54aa
to
48683cf
Compare
48683cf
to
ad9587a
Compare
58d68e6
to
af4e08d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another round of comments... Can we also add the annotations that set the indexes and constraints to the gorm models?
As discussed via MM, I would also like to confirm that null values (via manually inserted rows) do not break anything. (or, we just set annotations with the proper sql configs). |
840b0c3
to
e3129e7
Compare
e3129e7
to
265f569
Compare
6995d25
to
1ba26d6
Compare
cca2168
to
9337420
Compare
9337420
to
5c22ff1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is all good now, NULL values were also checked and the generated schema was reviewed so to have varchar
with reasonable sizes as opposed to longtext
.
The migration went through in test and we can go for QA.
Following ADR-Reva-003, this PR refactors the sharing SQL logic to now use GORM, an ORM for Go. This change also comes with newly written unit tests for all the database logic.