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

Created on 10 Mar 2017 · 12Comments · Source: dotnet/efcore

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

closed-fixed punted-for-2.0 punted-for-2.1 punted-for-2.2 punted-for-3.0 punted-for-3.1 type-bug

Source

alaatm

👍7

Most helpful comment

@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.

ajcvickers on 8 Sep 2019

👍4

All 12 comments

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

jpiquot on 12 Mar 2017

Can I request this issue be considered again. Here is the use case.

I am trying to write a SQL error handler that will produce a user-friendly error message from a unique index constraint. I can decode the SQL Server error message if its a single column constraint, but for multiple column indexes it is far harder as I cannot use the comma separators if some of the columns are varchar.

I would also like to alert users to possible duplicate errors where the errors come from a Soft Deleted entry, hidden by a Query Filter. That requires me to extract the property values and search for the duplicate item to detect if it was hidden by a Query Filter.

JonPSmith on 12 Oct 2018

👍1

@JonPSmith The issue is not closed; it is scheduled to be fixed in the 3.0 release.

ajcvickers on 12 Oct 2018

👍4

Did this make its way into EF Core 2.2? I don't see and code so I assume not. Be nice to have in 3.0

JonPSmith on 2 Apr 2019

@JonPSmith The milestone is set to 3.0. This means it's not in 2.2.

ajcvickers on 2 Apr 2019

Any news about this? The weekly status update does not mention the item and there is only one issue that's still being worked on for 3.0.

SebastiaanPolfliet on 2 Sep 2019

👍1

@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.

ajcvickers on 8 Sep 2019

👍4

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

Detzito on 4 Dec 2019

Re-triage based on https://github.com/dotnet/efcore/issues/15404#issuecomment-578224138

ajcvickers on 27 Jan 2020

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

roja on 11 Mar 2020

👍3

@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.

ajcvickers on 12 Mar 2020

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