I agree with the author that a separate table is the way to go, but I go one step further than the author and use database triggers to manage that second table.

I agree with the author that a separate table is the way to go, but I go one step further than the author and use database triggers to manage that second table. Alternatively, a combination of database views and triggers can do the same thing without having an actual extra table to manage. Either way, it allows you to have soft deletion and/or full activity logging functionality without the application having to know about it.