Not passing paramater value with @> PostgreSQL operator
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Using the Dapper ORM I'm constructing the following query to get a specific order from my PostgreSQL datastore:
$@"
SELECT * FROM ordertable
WHERE orderjson @> '{{""Lines"":[{{""SKUID"": ""@SkuId"" }}]}}'
";
Passing 123456-0 into the parameter @SkuId this construction should result into the following query
SELECT * FROM ordertable WHERE orderjson @> '{"Lines":[{"SKUID":"123456-0"}]}'
Dapper seems to ignore the paramater @SkuId as my query looks like
SELECT * FROM ordertable
WHERE orderjson @> '{"Lines":[{"SKUID": "@SkuId" }]}'
How do I use this @> operator ?
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 provides no repository file, test, or entry point. Start by reproducing the shown Dapper query against PostgreSQL and inspect how Dapper parses @SkuId alongside the @> operator; done means establishing whether the parameter can be bound and documenting or fixing the supported syntax.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, postgresql, sql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100