DapperLib / DapperLib/Dapper.Contrib
Identity column [Key] with varchar datatype not inserting
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 293
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
Hi Team,
Using Dapper.Contrib , attribute [Key] is defined for string variable(Here we are intending to use GUID as primary key for your database table).
Insert operation is failed, by throwing error "Column can not be null", but eventually GUI is passed in the variable.
Thanks
Varanasi
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 reported Dapper.Contrib insert with a string [Key] containing a GUID and a varchar primary key. Inspect the insert handling for identity keys and verify the expected database behavior; done means the non-null GUID is inserted successfully rather than producing a "Column can not be null" error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100