Valfrid Couto

Investigating this issue I could notice that version 1.6.3, even having a Async method always used the SYNC implementor. I'm still looking to fix it but I really need information...

Could you send an example how to reproduce the error?

Thanks, I'm going to check it out

Did you take a look into this test??? [UsingPredicate_ReturnsMatching](https://github.com/tmsmith/Dapper-Extensions/blob/2989ad7cb2f241276ce688ed3e05b320fec4cb56/DapperExtensions.Test/IntegrationTests/SqlServer/CrudFixture.cs#L229) It's exactly the same scenario and the test does not fail. I couldn't see any difference between tests. If there is...

@barry-tormey-imprivata , unit tests for PostgreSQL are being created. It's something we are missing to validate things that are particular to this database. @kitmax , I'll try to use the...

I'm still working on many things. I still have no date, but I'm trying to release a 1.7.1 with many bug fixes

I saw your changes and they are working but to approve your PR you need to add tests for all the supported databases not only SQL Server. The tests are...

Which is the error?

The support to net core are already in master branch and new version is supporting net core 2.1, 3.1 and Net 5.0

As it can be seen in the related issue is possible to use and DapperExtensions will map the result object. There is an example in the issue that was given...