Closed bsdayo closed 8 months ago
Interesting; this is indeed a minor change from Dapper; in vanilla Dapper, the behavior of string
is:
<= 4000
, set 4000
(using fixed value avoids constant recompilation with different inputs)-1
(which on various providers means max
)In AOT, it is:
[DbValue]
is specifed with a size, use that-1
This is clearly a change; I'll tweak it to behave identically to Dapper vanilla in the fallback scenario
1.0.26 is now available on myget, https://www.myget.org/F/dapper/api/v3/index.json - are you able to verify fix? (I don't have Oracle)
I apologize for the delay. I've been so busy lately that I forgot about it. I'm so sorry.
After upgrading everything works well. Thank you for the quick fix!
Describe the bug
I am trying to write my code with Dapper.AOT. When a simple query is executed with Oracle provider,
...the following exception is thrown:
When I look at the generated code, I see that the
Size
property is set to-1
, which caused the exception.Everything works fine without using Native AOT.
To Reproduce
The reproducible project is located here
Expected behavior
The query works.
Additional context