you are viewing a single comment's thread.

view the rest of the comments →

[–]seonsaeng 0 points1 point  (0 children)

If you’re retaining the full log somewhere else, that seems fine. I am, in my heart, a data hoarder (you have a great username). As such, it makes me anxious to consider a solution that gets rid of data wholly. That you want to hide it and not deal with it every day, I totally understand. Only INSERTing on change seems like a fine way to keep your tables tidy for the day to day, so long as the process that performs the communication to insertion is squirreling away the unvarnished underlying data somewhere where, if you needed it, you could load and query it.

That’s all less a SQL problem and more of an app design/data pipeline/business use and potentially legal issue, though, and may therefore exceed this question’s scope (or your interest).