3 ms·

If anyone feel interested after reading this comment, checkout the book called "Developing Time-Oriented Database Applications in SQL". edit: it contains many

If anyone feel interested after reading this comment, checkout the book called "Developing Time-Oriented Database Applications in SQL". edit: it contains many database-patterns that are useful even you aren't building time-oriented applications. It will make you a better developer. edit 2: basically, once you know some things from this book, every time you encounter a new database engine or programming language, the first thing you will want to look at is how the language handles dates & times - suddenly this kind of field become way more interesting. So the book might change how you view dates/times permanently, just be careful if you tend to over-engineer or are perfectionist, because it makes it easy to do so. Apply the patterns when it makes pragmatic sense.

sa46 5y ago
Good recommendation; I also got a lot of mileage out of: Managing Time in Relational Databases: How to Design, Update and Query Temporal Data How to Design, Update and Query Temporal Data > be careful if you tend to over-engineer or are perfectionist One of the downsides of these books is that I see bitemporal data everywhere now but its quite difficult to write bitemporal queries in Postgres.
- BatteryMountain 5y ago
  That's exactly what I mean. It's new lens and feels like it should be applied to everything, when it really should not. But then you start overthinking, that ~maybe~ your will regret not doing it etc. Silly I know.