Feature/last insert id support pg #4
Merged
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
DBI 1.38 is required at least to use last_insert_id https://metacpan.org/module/DBI#last_insert_id
alranel
added a commit
that referenced
this pull request
Aug 7, 2014
Feature/last insert id support pg
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.
I usually use DBIx::Lite with Pg and most of the time it works well. But currently DBIx::Lite does not support Pg for returning row object after
update(). I thinklast_insert_id()of DBI method will help_autopk()internal method of DBIx::Lite to support Pg. But I cannot sure thatlast_insert_id()is good or not rather than MySQL & SQLite's way. So I left them and just add for Pg.If there is no problem to support Pg, I hope I could install next release from CPAN. ;-)