Jonathan Magnan

Hello @jakehockey10 , The v3.0.20 has been released. We now support 3 versions: - `Z.Dapper.Plus` - `Z-Dapper-Plus` - `Z_Dapper_Plus` We will update our documentation in around 1 months to reflect...

Hello @himel951 , I do not think this issue will be fixed soon or ever. We don't put any focus on this library at this moment.

Hello @himel951 , It has been too long since we investigated this issue, so if there was a workaround, I don't remember it anymore ;(

Hello @Juandavi1 , Could you try without cache (`flags: CommandFlags.NoCache`) such as: ```csharp connection.QueryFirstOrDefaultAsync(new CommandDefinition(query, new { browserId}, flags: CommandFlags.NoCache, cancellationToken: cancellationToken)); ``` I might be wrong, but this sentence,...

Hello @Juandavi1 , I did some tests, and I was "right" and "wrong". Indeed, Dapper will cache depending on the connection string. So, the memory will grow the more you...

Hello @Alexn , Thank for reporting. Unfortunately, we don't have any solution at this moment to cover this scenario. We have the option `options.ForceOutputFromUnmodifiedRow = true;`, but it currently only...

Hello @Alexn , I should have said it in my first answer: you also need to select which properties you want to output. Here is a working fork from your...

Hello @suhaibans , I don't think something will be done here. Changing our code to be able to support Mocking is almost impossible in many scenarios. We instead recommend using...

Hello @zabulus , Let us know when you will have more information. I don't think this issue is fixed even using the latest version as it might be related to...

Hello @zabulus, Since our last conversation, we haven't heard from you. We will close this issue, if you provide more information we will re-open it. Don’t hesitate to contact us,...