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
Can´t use IsUnique when there is an item softdeleted, the validation ignore it and the DB return "Error: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry".
The text was updated successfully, but these errors were encountered:
I would suggest to not use soft delete on tables where the primary key is not generated.
However, you could always check before inserting if there are soft deleted records with the same primary key.
As for the validation, it should not ignore soft deleted records, how would you guarantee primary key uniqueness otherwise?
Can´t use IsUnique when there is an item softdeleted, the validation ignore it and the DB return "Error: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry".
The text was updated successfully, but these errors were encountered: