I could bundle all this up into a `@database.purge(@log_id)` call, which removed the log content and marks as purged?

Bundling marking as purged and archived into the same method on the database class feels like doing too much to me, and I don't really know what to name it.

Seems like there are two things to gain from bundling this into one method call (and therefore one SQL statement): Performance and atomicity. I don't think this query is *that* performance-sensitive, and these queries should be pretty fast anyways. Having the operations be atomic is a good idea, though, but I think we can solve this by wrapping things in a transaction instead.