DbUpdateException.Entries is empty when a unique constraint sql error is thrown.

[alaatm]

When a DbUpdateException is thrown because of unique index constraint, the DbUpdateException.Entries collection is empty. Is this an expected behavior or should it contain the involved entity in there?

Further technical details

EF Core version: 1.1.1

[jpiquot]

Hi,
I have the same issue on unique indexes or on primary key duplicates. The Entries value of the DbUpdateException is empty.

Regards

Versions:
EF Core version: 1.1.0
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10
IDE: Visual Studio 2017

[ajcvickers]

@SebastiaanPolfliet Unfortunately, it had to be cut from 3.0. However, it is scheduled for the 3.1 release scheduled for the beginning of December.

[Detzito]

I do also need it but it seems it has not been fixed in 3.1...

[ajcvickers]

Re-triage based on #15404 (comment)

[roja]

Any update on this? It stops us from recovering from unique collisions.

[ajcvickers]

@roja This issue is in the Backlog milestone. This means that it is not planned for the next release (EF Core 5.0). We will re-assess the backlog following the this release and consider this item at that time. However, keep in mind that there are many other high priority features with which it will be competing for resources.

[DeluxeAgency2020]

@ajcvickers Is any workaround for this issue with a performance problem?