My takeaway is (for applications that need this): #1: Keep rows immutable. Don't... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		ToBeBannedSoon on April 21, 2019 \| parent \| context \| favorite \| on: The Value of Bitemporality – Whose Time Is It Anyw... 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.

lichtenberger on April 21, 2019 [–]

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

ToBeBannedSoon on April 21, 2019 | [–]

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.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact