The Value of Bitemporality – Whose Time Is It Anyway?

Re:The Value of Bitemporality – Whose Time Is It Anyway? by ToBeBannedSoon on Sunday April 21, 2019 @01:28PM (#19713270)

My takeaway is (for applications that need this):

#1: Keep rows immutable. Don't use UPDATE or DELETE.

#2: Store the time columns you need, e.g. insertion or transaction time, and/or event generation time, etc.

[ Parent | on HN ]

Re:The Value of Bitemporality – Whose Time Is It Anyway? by lichtenberger on Sunday April 21, 2019 @02:27PM (#19713654)

Hm, and why storing so much information redundantly? Why not providing a tailored index structure... basically snapshotting page-trees efficiently :-)

[ Parent | on HN ]

Re:The Value of Bitemporality – Whose Time Is It Anyway? by ToBeBannedSoon on Sunday April 21, 2019 @02:51PM (#19713798)

If the db internally supports efficient temporal tracking, then yes by all means. If it doesn't, then I don't see a way for the developer around the redundancy.

[ Parent | on HN ]