-
Notifications
You must be signed in to change notification settings - Fork 278
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
add REGISTER_AUTO_KEY #129
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #129 +/- ##
==========================================
+ Coverage 39.88% 40.00% +0.12%
==========================================
Files 22 22
Lines 2856 2867 +11
==========================================
+ Hits 1139 1147 +8
- Misses 1717 1720 +3 ☔ View full report in Codecov by Sentry. |
REGISTER_CONFLICT_KEY |
https://wiki.postgresql.org/wiki/UPSERT#SQLite:...ON_CONFLICT....2F_INSERT.2FUPDATE_...OR... |
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.
LGTM
REGISTER_AUTO_KEY(person, id) used to set which field is the auto increment key;
for PG:
REGISTER_CONFLICT_KEY(student, code) only for PG: insert with update, more details:
https://www.postgresqltutorial.com/postgresql-tutorial/postgresql-upsert/