Anderson Matos
Anderson Matos
Confirmed this as a breaking change on my side as well. I had several legacy classes with properties which contain `_` as part of their names and this caused a...
IMO, the thing was that this is a major breaking change and we were not aware of it 🤣 TBH, so far, the feeling was that this was not intentionally...
Using int type as identity key results in an error (library always try to convert the value to long)
I found a workaround. If you change [this line from DapperImplementor](https://github.com/tmsmith/Dapper-Extensions/blob/master/DapperExtensions/DapperImplementor.cs#L702) as well as [this other line too](https://github.com/tmsmith/Dapper-Extensions/blob/master/DapperExtensions/DapperImplementor.cs#L706) to be like below, it would work out of the box. ```csharp...
Have you configured `DapperExtensions` to use `Postgres` dialect? ```csharp DapperExtensions.DapperExtensions.SqlDialect = new DapperExtensions.Sql.PostgreSqlDialect(); ``` If yes, then this is likely a duplicate of https://github.com/tmsmith/Dapper-Extensions/issues/273
Sorry for the delay. Here's some tech details: - AspNet on .NET 5.0 - SQL Server 2019 installed on Windows Server 2019 (virtualized). All patches applied on both Windows and...
I won't lie: today it is. I prefer to take the honest path and tell you (all) this. So, let me put into context. I'm on a dead-end here now....