When rendering SQL, only render the alias if it's different from the table name #3045
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 DBAL is used as part of a higher level abstraction where queries are built dynamically, the table name and the alias in
SELECT
,UPDATE
andDELETE
queries may be defined independently and may end up being the same. In this case, the resulting SQL contains a redundant alias:…which is technically valid but not needed. In order to avoid that, the caller needs to compare
$table
and$alias
before calling$builder->from()
(in the case above) and passnull
as the alias in the case if they are equal.The caller logic could be simplified without an impact on generated SQL if the DBAL itself only rendered the alias if it's different from the table name.