Valfrid Couto

Could you send your mappings please and how to reproduce the error?

It's is not without attention but I'm wating for more information. If you know how to reproduce, please walk me thru it I have this in use on a company...

Thanks for the help @thefat32 , I'll be looking for the implementation of the solution

In the new version we'll have the possibility to assign DBType, Direction and other parameter options. It should solve this problem

It is fixed in the next version as the type was moved from int to long and it's now a 64bit integer.

I accept suggestions when you have reference maps if this is changed. Basically, when you have a joint table the properties will be like Class1_PropertyName. The change in the closed...

Still trying to find. The results are comming directly from Dapper and not being mapped.

Is this the only table with this issue???

@aravindk777, tables are declared "SCHEMA_NAME"."TABLE_NAME". Lets remember that Oracle IS case sensitive. If you declare a table name "test" and another one as TEST they will be different. Usually people...

We have to use long as these identities can get very big. If you do not apply "Type" to the mapping it should work normally.