Dapper mapping String parameter as AnsiString

Question

I need to pass parameters to SQL statement, with Firebird ADO everything works well, but with InterBase ADO there is a problem. My code:

result = conn.Query<DestClass>(sqlCmd, new
{
  stringParam = stringVal,
  intParam1 = intVal1,
  intParam2 = intVal2
}).Single();

With that I've got FormatException, but when I define parameters with DynamicParameters and setting DbType.AnsiString for stringParam, SQL works well. But I've got many places in my code when I need to pass string and I don't want to change this in all places.

Then I found that I can use Dapper.SqlMapper.AddTypeMap(typeof(String), DbType.AnsiString); but I can't. I've got Common Language Runtime detected an invalid program.

How to resolve this issue?

EDIT

It looks like problem is solved in Dapper v1.22.

Marc Gravell · Accepted Answer · 2014-05-08 16:17:08Z

3

There is a proposal to add an assembly-level attribute of the form:

[assembly:SomeName(blah)]

that would control the default string type for all types coming from that assembly. This would probably achieve most of what you need (although it would push the swing the other way, so you need to tell the other uses what to do). I am currently very actively hacking dapper, so I would expect this to materialize in the short term.

Note that you do not need to use DynamicParameters; you can also use:

stringParam = new DbString { Value = stringVal, IsAnsi = true }

answered May 8, 2014 at 16:17

Marc Gravell

1.1m273 gold badges2.6k silver badges3k bronze badges

Sign up to request clarification or add additional context in comments.

10 Comments

to StackOverflow Over a year ago

Interesting proposal, but my gut reaction is to be uncomfortable with the idea of an API who's behavior depends on an attribute in the calling assembly. What about performance, inlining and maintainability (specifically the fact that behavior could change by moving a class into a different assembly)?

Marc Gravell Over a year ago

@Joe il-merge would indeed complicate things

Marek Ruszczyk Over a year ago

Thanks for response, but stringParam = new DbString { Value = stringVal, IsAnsi = true } is not working. Only when I pass parameters with DynamicParameters it works fine. Could you explan to me how should I use [assembly:SomeName(blah)]?

Marc Gravell Over a year ago

@MarekRuszczyk to emphasize: that is simply a proposal at this point. For you to use that, I need to write the code. I will check on the dbstring, though - that should work.

Marc Gravell Over a year ago

@MarekRuszczyk this works fine: pastie.org/9158605 - can you be more specific about the scenario that isn't working?

|

Collectives™ on Stack Overflow

Dapper mapping String parameter as AnsiString

1 Answer 1

10 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

10 Comments

Your Answer

Sign up or log in

Post as a guest

Related