-
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
[6.0] Fix SQL Server NTS scaffolding code generation #26160
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reiterate my concern over testing/validation in this area.
This was indeed a change with some far-reaching consequences - I did do my best to proactively add test coverage etc., but clearly some things slipped through. I can look at the change again with fresh eyes to try to flush out more issues, though it may also be more productive if someone else helps with this. |
@roji I'm thinking about. Let's discuss in triage tomorrow, assuming you're around. |
Let me know if I can help in any way? |
I probably won't be (we can discuss earlier if you want)... But in any case am OK with whatever you decide. |
Approved for EFCore 6.0 |
Following dotnet/efcore#26160 (cherry picked from commit 126a6b6)
Fixes #26133
Description
An incorrect type reference prevents scaffolding from working correctly when NetTopologySuite is used.
Customer impact
Customers cannot scaffold databases when using the NetTopologySuite spatial plugin.
How found
Customer
Regression
Yes
Testing
Test for this scenario added in the PR.
Risk
Very low, the fix is trivial and affects scaffolding only (no runtime impact)