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.
Of all supported platforms, only PostgreSQL allows to omit the name in the
CREATE INDEX
statement (it will generate it internally). The rest of the platform require the index name to be defined as part of their syntax.Handling of the
null
value of the$name
name parameter of theIndex
constructor was added in #2854. Quite likely, it was done in order to satisfy a test for the code that would use an index to create a primary key constraint. Thus, there was a false assumption that given that constraints can be unnamed, indexes should be as well (see #2854 (comment)).Unlike foreign key and unique constraints, for which DBAL generates the name, if it's omitted in the definition, it doesn't do that for indexes, so two indexes with empty name cannot even co-exist in a table definition: