DapperLib / DapperLib/Dapper.Contrib
dapper contrib with oracle
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 293
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
I find 2 issues about dapper.contrib with Oracle.
1.with function insert,update,delete,all of them has the bug that dapper.contrib only support the placeholder '@', in the meantime, Oracle is only support placeholder ':' whicn cause the problem.
2.in Oracle,if the primary key is set to auto-increment, you need add ".nextval" in sql while insert some data.because the difference between tables,primary key always different from each other too.I have no good solutions.
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 tracing how Dapper.Contrib implements insert, update, and delete placeholders, then examine how Oracle auto-increment primary keys are handled during inserts. Clarify whether each table's sequence should be configured or discovered, and define completion as Oracle-compatible placeholders and correct primary-key behavior for all affected operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- database
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100