6 ms·
> bitemporal schemas are difficult with regard to cross-table references Who needs more than one table ? >:) More complex models can be built and stored separ
by pyrale 2y ago
> bitemporal schemas are difficult with regard to cross-table references
Who needs more than one table ? >:)
More complex models can be built and stored separately. The great benefit of this method being that, once you're unhappy with your table model, you can trash it and rebuild it from scratch without regard for data migration.
- layer8 2y agoYour last sentence sounds more like event sourcing than bitemporal databases, which are quite different concepts. I don’t see how bitemporal schemas simplify schema migration.
- pyrale 2y ago> I don’t see how bitemporal schemas simplify schema migration. It's not the bitemporality that helps, it's primary data immutability. The event sourcing community has its own specificities (event sourcing advocates saving decisions, not outside data), but not on that aspect: if you store events immutably as this article describes, you are bound to benefit from read models that you can trash and rebuild at will.