Error on Postgres `ENUM` on first run about dapper

[mgravell]

Dapper knows literally nothing about postgresql enums; I can only presume that this is handled internally inside Npgsql, with Npgsql building a cache of known types when needed, hence if you add types: it doesn't immediately know about it. Note that Dapper.AOT is in the process of adding more enum support (it doesn't exist today), which will use a different API rather than the object API; this may change how this works with Npgsql, hopefully for the better!

[mgravell]

To clarify: the enum handling in AOT is going to switch to using GetInt32 etc (insert appropriate type here), hence it sounds like Dapper.AOT's changes will indeed remove some overheads and problems here. That'll probably get done over the festive period.

[rick-micpoint]

Thank you for your quick response! Looks like it wasn't related to dapper after all. Calling ReloadTypesAsync on the connection after every migration fixes the issue.

[mgravell]

It was actually very welcome, though - it hints at some tangible side benefits to the ongoing enum work, so: yay