DapperLib / DapperLib/DapperAOT
Do ODBC parameters work yet?
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 472
- Forks
- 43
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 18
Description
I am trying to use Dapper.AOT with an ODBC data source, and the usual patterns for ODBC parameters don't seem to work.
Am I doing something wrong? Are there plans to support this?
Thanks!
Old positional style:
var result = await connection.QueryAsync<SomeType>("select Col1, Col2 from Table1 where Key = ?", new { key });
Old named style:
var result = await connection.QueryAsync<SomeType>("select Col1, Col2 from Table1 where Key = ?key?", new { key });
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 two QueryAsync examples against the ODBC data source described in the issue, checking both positional and named parameter styles. Determine the intended support scope and use that to define what a complete change would need to demonstrate; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100