You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@oldtrafford91 Good catch – this happens because of a uniqueness constraint conflict on a Country or Continent entity. Those entities have a uniqueness constraint defined (using the numericISO3166Code attribute. However, this uniqueness constraint should also include the markedForDeletionDate attribute to allow deleted and non-deleted instances of a country/continent to co-exist. I'll push an update to the code, let's see if that fixes it.
Activity
floriankugler commentedon Jan 1, 2016
@oldtrafford91 Good catch – this happens because of a uniqueness constraint conflict on a
CountryorContinententity. Those entities have a uniqueness constraint defined (using thenumericISO3166Codeattribute. However, this uniqueness constraint should also include themarkedForDeletionDateattribute to allow deleted and non-deleted instances of a country/continent to co-exist. I'll push an update to the code, let's see if that fixes it.floriankugler commentedon Jan 1, 2016
@oldtrafford91 unfortunately this doesn't behave the way I expected it to... will think a bit more about what's a good solution.