[postgres] Distinguish empty and NULL values #5483
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
m-kuhn
force-pushed
the
postgisEmptyValue
branch
from
f30cfe0
to
f3db991
Compare
m-kuhn
force-pushed
the
postgisEmptyValue
branch
from
f3db991
to
76746e7
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.
Right now adding a feature with an empty string attribute to postgres will add a feature with a NULL value, if constraints are in place for this attribute.
This is especially painful when we have a string field with a
NOT NULLconstraint. Leaving the line edit on the form empty, it will be reported as valid with a green tick, the database will complain about the value being invalid on insert.