Fix computed columns mapping to wrong tables #51009
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.
If at least one table contains a computed column,
Schema::getColumns()
would show the computed column for other tables as well.The query created by
\Illuminate\Database\Schema\Grammars\SqlServerGrammar::compileColumns
is missing a join predicate betweensys.columns
andsys.computed_columns
:This adds the predicate to ensure only computed columns that belong to the current table are returned.
Tested on SQL Server 2019.