-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Scaffold uses system's comma separator for HasDefaultValue #35654
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
Milestone
Comments
Please share the full CREATE TABLE statement |
I created a minimal example
|
ErikEJ
added a commit
to ErikEJ/EFCorePowerTools
that referenced
this issue
Feb 21, 2025
Looks like this method signature should have been used: @roji Happy to submit a PR! @Quietscheente I have fixed this in the latest daily of EF Core Power Tools |
ErikEJ
added a commit
to ErikEJ/EFCorePowerTools
that referenced
this issue
Feb 21, 2025
Sure, that'd be great! |
This was referenced Feb 24, 2025
Would be possible to merge this fix into 8.0.x release? |
@zimaa77 The fix is in EF Core Power Tools CLI for EF Core 8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
I have a german Windows 10 and with Scaffold (8.0.8)
a default value set in the database (SQL Server 13.0) with
ALTER TABLE [dbo].[Foo] ADD CONSTRAINT [DF_Foo_weight] DEFAULT ((1.0)) FOR [weight]
becomes aentity.Property(e => e.Weight).HasDefaultValue(10.0);
in the DbContext.
If I change the comma separator in the Region settings to "." it is
HasDefaultValue(1.0)
as expected.Your code
Stack traces
Verbose output
EF Core version
8.0.8
Database provider
No response
Target framework
.NET 8
Operating system
Windows 10
IDE
No response
The text was updated successfully, but these errors were encountered: