[Fix #54502] Retrieve column from connection's schema cache when computing default attribute types #54510
+11
−0
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.
Motivation / Background
Fixes #54502 (I've tested against that repro script)
Some discussion in https://discord.com/channels/849034466856665118/974005005768069211/1339360740057944075
Detail
Ensures columns used when defining default attribute types are retrieved from the schema cache for the current connection instead of from the model schema, which may have been set by different connection in another thread.
I've targeted
7-2-stable
cause this doesn't really make sense onmain
, and we'd want to do the same for8-0-stable
. Alternatively as I mentioned in the issue we could backport 9ad36e0.Checklist
Before submitting the PR make sure the following are checked:
[Fix #issue-number]