-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[5.0.3] Flow through the column types in MigrationBuilder.InsertData #23614
Conversation
@AndriySvyryd I assume |
Tactics would like us to wait for more customer reports on this one given that this, "only affects new API that is seldomly used." |
Ok. Any time it's used it will fail. |
@AndriySvyryd If we get more customer reports we can take it in the next patch. |
@ajcvickers That's fine, I'm not pushing back |
d8ab3a3
to
410c551
Compare
Fixes #23503
Note for Tactics
This was rejected for 5.0.2 due to concerns that it might not impact many customers. We now have multiple customer reports (4+) so we're brining it back for 5.0.3.
Description
MigrationBuilder.InsertData
was not passing through the column types parameter to the underlying method.Customer Impact
Creating a migration that adds data to a table that is not mapped in the model will fail. The workaround would be to use internal API.
How found
Customer reported on 5.0.0.
Test coverage
We have added more test coverage in this PR.
Regression?
No, this overload of
InsertData
is new in 5.0Risk
Low. Only affects new API that is seldomly used.