Introduce DB#InsertObtainID() function
#64
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yhabteab
requested review from
lippserd,
julianbrost and
oxzi
and removed request for
lippserd and
julianbrost
oxzi
reviewed
Aug 15, 2024
yhabteab
force-pushed
the
last-insert-id
branch
from
2045ba4
to
1317301
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces an auxiliary DB function for inserting and retrieving the last inserted ID with both the
PostreSQLandMySQLdrivers. Since the MySQL driver supports/providesLastInsertId()natively, there's nothing special that this function needs to do. On the other hand, PostgreSQL doesn't provide such functionality on its own, so you have to append a specialRETURNING idtext to the query you want to execute and scan the result into a given dest of your own.cherry-picked from #18