DapperLib
DIPSAS Dapper.Oracle is Deprecated - migration path?
This is a support request really, and I know this isn't the correct project, but I assume issues over there are going to go unanswered...
We use Dapper.Oracle quite extensively with our Oracle database. Does anyone know if there's a migration path for people currently using Dapper.Oracle / OracleDynamicParameters? Is that functionality becoming part of Dapper itself, or is there a recommended supported library to migrate to?
Just a cursory look, and it doesn't seem like I can replace the Oracle specific code with anything in the Dapper DynamicParameters class, and maintain the same functionality.
Assume that we don't know / use Dapper.Oracle. What is the specific functionality / behaviour that you're looking for? If you're after fine-grained provider-specific parameter configuration, then that might be possible via the AOT bits (now or in the future), although I'd need to check on a case-by-case basis.
Yes it's about more fine grained parameter control. For example, working with CLOB types.
Now, I haven't tried porting what we have currently. I know I've run into a few things with both open and closed issues: #142 , #1416 . I also have some package procedures that I call using the Dapper.Oracle PLSQLAssociativeArray type (this may work to replace with a DataTable??). Some of the issue workarounds look to use custom parameter types, which I'm not really familiar with. And then there's the FetchSize #654 that's come up a few times.
That said I've also run into bugs with Dapper.Oracle that I have not been able to work around and had to fall back to Dapper's own DynamicParameters() (passing lists to IN clauses if I remember correctly).
I see you mentioned DapperAOT, which is something I have not looked into at all. Is that production ready? Does it help to solve any of these Oracle specific issues?