Would using temporary tables be a feasible solution? That seems to be functionally what I want, but maybe it's hard to write triggers that write to temp tables.
Maybe a persistent log table is OK, and each transaction is responsible for deleting its own rows from it? Sounds like a lot of churn though...
Maybe that would be useful. I've never used them, though, so don't know any gotchas.
Thanks for the suggestion. That seems semantically close to what I'm looking for. In my case we're working with Amazon RDS, so I don't think ad hoc extensions are permitted.
This communication and any attachments may contain confidential information and are intended to be viewed only by the intended recipients. If you have received this message in error, please notify the sender immediately by replying to the original message and then delete all copies of the email from your systems.
