Hacker News Reader

While that's kind of convenient in a lot of ways, it also makes querying the database really annoying, since you have to remember to add the filtering to every single query or you're screwed. Personally, I wish there was a database-implementation-acknowledged "deleted" flag, which could even expose a "history table"-like interface.

How does using a timestamp column make querying the database more annoying than using a boolean column? Aren't the places you have to use filters exactly the same either way?

I'm sorry, I wasn't being clear. Any column meaning "this row is to be ignored for most applications" is an annoying pattern.

Ah, now I see I responded to the wrong message.

This makes more and more sense the more I think about it

I can vouch for this pattern from personal experience. From an auditing perspective also, it can be really helpful to know WHEN something was removed.

Interesting, I’ve never heard about that pattern, only is_deleted everywhere

That's a good idea.

I love this pattern

this seems neat!