Have you considered using transaction processing? At the same time, the poster can change his mind and add this record to the backup table first, and then delete this data. Don’t worry, this process must use transactions to maintain event consistency!
Use triggers to implement this, but this is not recommended. You can add a field to the table to mark it as deleted
Have you considered using transaction processing? At the same time, the poster can change his mind and add this record to the backup table first, and then delete this data. Don’t worry, this process must use transactions to maintain event consistency!
Possibly the trigger will have the least impact on the existing system and require the fewest conditions to be met