daviden83

Only occasionally. But recompiling, even without changing anything in the source code, the problem generally disappears.

I would also add that the model that I pass to the GetById method actually has a difference compared to all the other models, i.e. the presence of this method:...

Unfortunately for me, after months that the problem had never reappeared, last week it happened again and with a stored procedure that always returns only a set of results. Obviously...

The problem has never occurred to me anymore, without making substantial changes to the way I make database calls.

Sometimes the problem recurs and often on a different stored procedure from the previous one. A recycle of the application pool in IIS is sufficient to solve the problem. But...

I use this method to log any SQL exception: ``` c# private void LogSQLError(Exception ex, string commandText, object pars, CommandType commandType) { string parsString; if (pars is DynamicParameters dynPars) {...

No I have not tried, also because generally the Dapper methods do not have problems of case sensitivity with the parameter's names, in fact this is a problem that occurs...

I was able to reproduce the problem. It occurs when calling the same stored procedure first with the QueryMultipleAsync method + ReadResultAsync and then with the QuerySingleOrDefaultAsync method (also with...

From what I have noticed, the problem occur in exactly this case: 1. A stored procedure is first called by the QueryMultiple method. 2. Parameters are passed using a DynamicParameters...

@mgravell Any news about my latest posts? The test posted by pblackburn68 also highlights the problem: https://github.com/DapperLib/Dapper/issues/1430#issuecomment-760516483