Formatting from DB Date into C# string is not using current culture (Dapper Nugget package 2.1.28)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Thx for the cool ORM!
We use legacy code.
I upgraded Dapper from 2.0.30 to the Latest (Nugget package 2.1.28)
And now date is formatted to string always without respecting current culture.
With old Dapper version 2.0.30 , when change current culture to "lv-LV" and Query from Oracle, db Date field into C# string field formatted correctly "dd.mm.YYYY".
With Dapper 2.1.28 its always "mm/dd/YYYY" regardless of culture.
( Receiving Date Ok. Yeh, we should keep as C# Date, but that another story - legacy)
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
Start by reproducing the upgrade from Dapper 2.0.30 to 2.1.28 with an Oracle date queried under the lv-LV culture and mapped to a C# string. Done means the mapped string respects the current culture in the newer package, with the behavior verified against both versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100