Home/ Questions/Q 5975347
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T21:04:19+00:00

We use Oracle as our database provider and have looked into replacing some of

  • 0

We use Oracle as our database provider and have looked into replacing some of our data access layer (hard to maintain, harder to merge XSD’s) with a saner repository based pattern using Dapper at the bottom layer. However, we have hit a number of issues when using it with oracle.

  • Named Parameters: these seem to be ignored, whenever they are used in a query Oracle seems to interpret them in any order it fancies. The SqlMapper returns correctly named parameters, they just aren’t interpreted correctly in Oracle

  • The “@” naming convention for variables is incompatible with oracle named parameters. It expects to see “:” in front of any parameters

Has anybody previously encountered this and have any workarounds?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    IMO, the correct approach here is not to (as per the accepted answer) use the database specific parameter prefix (so @ for sql-server, : for oracle) – but rather: use no prefix at all. So ultimately this is:

    il.Emit(OpCodes.Ldstr, prop.Name);

    (etc)

    In particular, a static property would be bad as it would limit you to one vendor per AppDomain.

    Dapper has been updated with this change. It also now dynamically detects BindByName and sets it accordingly (all without needing a reference to OracleCommand).

    • 0