"NULLS NOT DISTINCT" for indexes in PostgreSQL 15+ #1814
Merged
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 pull request adds support of "NULLS NOT DISTINCT" option for PostgreSQL.
By default, unique indexes in PostgreSQL allow multiple null values (so, null values are considered not equal to each other). In PostgreSQL 15, new option was added: "NULLS NOT DISTINCT", which allows only single null value.
https://www.postgresql.org/docs/current/sql-createindex.html
Before PostgreSQL 15, there was a workaround with two indexes: https://stackoverflow.com/questions/8289100/create-unique-constraint-with-null-columns
To enable "NULLS NOT DISTINCT" for index, UniqueNullsNotDistinct method should be called:
Runner should be configured with AddPostgres15_0: