4 ms·
No. Just no. Put created_at, updated_at on every table. You are really grasping to find a problem with it, because there isn't one, and its been helpful in lite
by jeremyjh 2y ago
No. Just no. Put created_at, updated_at on every table. You are really grasping to find a problem with it, because there isn't one, and its been helpful in literally every job I've had for the last 28 years. Product owners don't do application support.
- crazygringo 2y agoNo, just no, back at you. That's not all the article was suggesting. You're ignoring the other three fields the article says to "store on almost any table". I'm not "grasping", I'm describing actual reality. While you're misrepresenting the article by cherry-picking the simplest fields, which aren't even always simple for the reasons I gave.