PG: identify pk when exporting #45375
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
When exporting a layer, if no PK information is passed in the destination URI, the first numeric field with NOT NULL and UNIQUE constraints is considered to be the primary key. Partial fix for qgis#45286
elpaso
added
Bug
nyalldawson
approved these changes
Oct 4, 2021
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.
When exporting a layer, if no PK information is
passed in the destination URI, the first numeric field
with NOT NULL and UNIQUE constraints is considered to be
the primary key.
Partial fix for #45286
Notice that I'm not really sure this is a bugfix or a feature, feedback welcome.