Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Desmark [Column(TypeName = "decimal(18,0)")]
See original GitHub issueMark off
This annotation is bad for those who use if and else in procedures. How to uncheck it?
[Column(TypeName = "decimal(18,0)")]
Provide technical details
-
EF Core version in use: 6
-
EF Core Power Tools version: 2.5.1429
-
Database engine: (SQL Server)
-
Visual Studio version: 2022
Issue Analytics
- State:
- Created 3 months ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Decimal precision and scale in EF Code First
I'm experimenting with this code-first approach, but I'm find out now that a property of type System.Decimal gets mapped to a sql column...
Read more >No Type Was Specified for the Decimal Column
No type was specified for the decimal column 'Size' on entity type 'Part'. This will cause values to be silently truncated if they...
Read more >Entity Properties - EF Core
Included and excluded properties; Column names; Column data types ... [Column(TypeName = "decimal(5, 2)")] public decimal Rating { get; set; } ...
Read more >HasPrecision() does not override [Column(TypeName= ...
i.e. no precision or scale specified in the SQL data type, so SQL Server at least would use its default of decimal(18,2). .HasColumnType(" ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Makes sense, I will look into making it optional
I implemented a fix for this in the latest daily build, would be grateful if you could try it out.
If you like my free tools, I would be very grateful for a rating or review on Visual Studio Marketplace or even a one-time or monthly sponsorship