Closed wazzamatazz closed 10 months ago
I think the reason is, the AcquireCommand returns now a null value instead of DBNull.
Any workaround?
@Kaffeetasse appreciate the diagnosis. Seems like this is a breaking change in Npgsql (I wonder if it is intentional).
fixing this in the package would be very easy; we can simply detect when it gets the “wrong” value and convert to what we expect.
I’d be happy to look at a PR for this. Otherwise, I can hopefully get to it in a few weeks.
Any time when someone will find time to review and release it?
@valentasm1 I should be able to do it in the next few days.
I'm using DistributedLock.Postgres in a project that is using EF Core 7 and Npgsql 7. If I update the project to use EF Core 8 and Npgsql 8 RC2 I am no longer able to acquire a lock. Instead, I see an error and stack trace like the following:
I am creating the lock by passing the connection string to the
PostgresDistributedLock
constructor rather than anIDbConnection
instance but I've found that I get the same error regardless of which constructor I use.Reverting to EF Core 7/Npgsql 7 immediately fixes the issue.