I was about to suggest a view, but then I realized that's just a transparent window to the data, not a way to actually store the history. Trigger is the clear winner here. Unless, of course, you want to add some spice and go with a process model. You know, really make things complicated.
A trigger is definitely the way to go here. It's like a ninja in the shadows, silently recording every row that gets deleted. Efficient and stealthy, my kind of solution!
Hmm, I think a trigger would be the most efficient way to handle this. Automatically inserting the deleted row into a history table seems like a pretty straightforward use case for a trigger.
Annett
1 months agoElbert
2 days agoEttie
7 days agoShawna
13 days agoMuriel
27 days agoShelba
1 months agoIndia
2 months agoMiesha
9 days agoMiesha
12 days agoMike
2 months agoBrittani
2 months agoLorrine
2 months agoFiliberto
2 months ago