Conversion overflows error appear after the decimal point decimal(38,12)
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
after the decimal point 12 appear Conversion overflows error
for example decimal(38,14)
we use decimal(38,20) in project
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source file, test, or exact query. Reproduce the reported decimal(38,14) and decimal(38,20) conversion cases in a minimal Dapper/ADO.NET example, then locate the conversion path and add regression coverage; done means the reported values no longer overflow and existing tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100