You will find validations in position which should not allow a replica record inside a particular table to become produced according to two different ID values (the first is a person ID) along with a condition (some states are permitted to possess replicates, although not others).

Whenever we get two demands, one to another within the logs with similar time stamp, the very first record isn't within the database to result in the rejection from the second record. It's very odd since the two demands come from different Insolvency practitioners, but possess the identical information (perhaps a reply attack from the jeopardized computer?).

I was considering developing a unique index around the database, however it will not work since only certain states for records ought to be checking for originality.

It is possible to approach we take to can produce a database constraint, validation constraint, demands constraint or something like that else to assist avoid this?

Thanks!