[12.x] Add support for PostgreSQL "unique nulls not distinct" #55025
Conversation
This file contains hidden or 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
thierry2015
changed the title
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.
What
This adds support for PostgreSQL (
>= 15)unique nulls [not] distinctwhen building unique indexes.Why
The only way to execute such a statement inside a migration at the moment is to wait after the table creation (outside the
Schema::create()statement, as AFAIK there's no way to inform the blueprint of a custom command to be executed) or by extending the Postgres schema grammar (idea thread)How
By adding support for a new
nullsNotDistinct()fluent index definition method (see the unit tests for some examples) when using thepostgresdatabase driver (or more precisely when using the Postgres schema grammar).Benefits
Developers will now be able to use this native PostgreSQL feature, which could reduce the scope of work when building a feature requiring unique database record combinations, including null values.