Custom type handlers for enums are ignored

[chilversc]

I have an enum that is serialized to the DB using a single letter code.
I tried adding a custom type handler for the enum to handle the conversion but dapper seems to ignore the custom type handler.

Given the example code I expected to see the values;
ID = 10, Type = B
ID = 1, Type = Foo

What I actually got was:
ID = 1, Type = 2
DataException, Error parsing column 1 (Type=F - String)

---

void Main()
{
 SqlMapper.AddTypeHandler(new ItemTypeHandler());
 using (var connection = new SqlConnection("Server=(local); Database=tempdb; Integrated Security=SSPI")) {
 connection.Open();
 connection.Query ("SELECT @ID AS ID, @Type AS Type", new Item {ID = 10, Type = ItemType.Bar}).Dump();
 connection.Query<Item> ("SELECT 1 AS ID, 'F' AS Type").Dump();
 }
}

class ItemTypeHandler : SqlMapper.TypeHandler<ItemType>
{
 public override ItemType Parse(object value)
 {
 var c = ((string) value) [0];
 switch (c) {
 case 'F': return ItemType.Foo;
 case 'B': return ItemType.Bar;
 default: throw new ArgumentOutOfRangeException();
 }
 }

 public override void SetValue(IDbDataParameter p, ItemType value)
 {
 p.DbType = DbType.AnsiStringFixedLength;
 p.Size = 1;

 if (value == ItemType.Foo)
 p.Value = "F";
 else if (value == ItemType.Bar)
 p.Value = "B";
 else
 throw new ArgumentOutOfRangeException();
 }
}

class Item
{
 public long ID { get; set; }
 public ItemType Type { get; set; }
}

enum ItemType
{
 Foo = 1,
 Bar = 2,
}

[wwarby]

I've just hit exactly the same problem. It seems like SqlMapper handles enums differently than every other type and tries to map them with Enum.Parse even if a custom type handler is specified. I'm just about to delve into the source and see if I can see an easy fix - I'll report back if I find anything useful.

[wwarby]

Urgh. I knew Dapper was optimised for performance but I didn't realise it literally emitted IL op codes to do value conversions. No chance I'm ever going to get to make enough sense of the source to offer up my own solution to this one so I'm hoping the devs will accept this as an enhancement.

[chilversc]

I don't thing you need to touch the IL sections. It's mostly a case of changing the order of the type checks to look for a custom handler first. At the moment it checks if it's an enum before it checks for custom type handlers and thus never discovers the custom type handler.

My only concern is that I'm not sure what impact that will have on the rest of the system since similar type checks are in other places.

Backwards compatibility shouldn't be a concern since it has never worked in the past I doubt anyone will have custom handlers for primitive types such as enums.

[mgravell]

Enums have quite a few nuances and special cases. I'm sympathetic to what
you want to do here, but it isn't trivial - I'll need to have a look at it
with a clear head.

On 10 April 2015 at 20:11, Chris Chilvers notifications@github.com wrote:

I don't thing you need to touch the IL sections. It's mostly a case of
changing the order of the type checks to look for a custom handler first.
At the moment it checks if it's an enum before it checks for custom type
handlers and thus never discovers the custom type handler.

My only concern is that I'm not sure what impact that will have on the
rest of the system since similar type checks are in other places.

Backwards compatibility shouldn't be a concern since it has never worked
in the past I doubt anyone will have custom handlers for primitive types
such as enums.

—
Reply to this email directly or view it on GitHub
#259 (comment)
.

Regards,

Marc

[vdaron]

I would like to be able the same for the generic System.Enum type to change the serialization behaviour of all Enums (I'm using attributes to specify the letter used to serialize an Enum)

First check for a

 SqlMapper.TypeHandler<ItemType>

then for a

 SqlMapper.TypeHandler<Enum> 

(the default Dapper behaviour could be specified that way too)
Thanks for your interest on this feature @mgravell

[otac0n]

@mgravell I worked on this a bit yesterday, and came up with this:

otac0n@817fa95

It works for everything I've tested, but I haven't written any unit tests for it.

I was testing it with this Type Handler:

public class StringEnumTypeHandler<T> : SqlMapper.TypeHandler<T> where T : struct, IConvertible
{
 static StringEnumTypeHandler()
 {
 if (!typeof(T).IsEnum)
 {
 throw new ArgumentException("T must be an enumeration type");
 }
 }

 public override T Parse(object value)
 {
 return (T)Enum.Parse(typeof(T), Convert.ToString(value));
 }

 public override void SetValue(IDbDataParameter parameter, T value)
 {
 parameter.Value = value.ToString();
 parameter.DbType = DbType.AnsiString;
 }
}

This doesn't support @vdaron's use case, however.

[ShamsulAmry]

@vdaron, thanks for the reference. Didn't make an effort to check that this issue was already logged, my bad.

My use case is exactly the same as what @chilversc tried to achieve - single letter code in DB to represent an enum value. But it does not support @vdaron's "fall back" behavior request though.

@mgravell, my commit in issue #286 included relevant test code and "all green" tests.

[roji]

+1

[drusellers]

I've run into this as well. :(

[kbilsted]

What is the status of this issue?