TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Bitemporal History

64 点作者 r4um大约 4 年前

8 条评论

lmilcin大约 4 年前
As we are working on complex trading systems it is frequently necessary to correct past record and then be able to make consistent reports based on &quot;as of&quot; date. This means answering questions like &quot;I want to get the state of this population of trades as it was yesterday at 5 pm but based on our knowledge yesterday at 10 pm.&quot;<p>Pretty fun actually when you have billions of these records:)
jacobobryant大约 4 年前
Shout out to Crux (<a href="https:&#x2F;&#x2F;opencrux.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;opencrux.com&#x2F;</a>), a bitemporal database. I&#x27;ve been using it for a year now and it&#x27;s fantastic.
评论 #26744895 未加载
Hettie大约 4 年前
Check out our framework for bitemporlity: <a href="https:&#x2F;&#x2F;github.com&#x2F;scalegenius&#x2F;pg_bitemporal" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;scalegenius&#x2F;pg_bitemporal</a> We use it in production for 5 years. I am ready to answer any performance&#x2F;indexing and other questions
helsinki大约 4 年前
I have not read the article, but I have written a bi-temporal ORM, and I find it to be such a useful concept in practice. One of the primary benefits is optimistic locking. You can say goodbye to explicitly locking during a db transaction.
评论 #26744736 未加载
thelittlenag大约 4 年前
I ran across this notion for the first time when I started a job in finance a few years back and as an interview question they asked me about it. I hadn&#x27;t heard of the notion and so afterwards tried to find some good resources online to read up about it.<p>What I found was not great. So glad to see this idea getting a good write up.
评论 #26745083 未加载
nyanpasu64大约 4 年前
Reminds me of rebasing Git branches in order to clean up commit histories, or rewriting Git repositories in order to change usernames&#x2F;emails stored inside.<p>I just hope that whatever systems get created (bitemporal history, version control, etc.) have support for &quot;replacing&quot; previous usernames, or deleting events prior to a specific &quot;record time&quot; and replacing them with newer understandings of history. Doing so in Git (a more-or-less append-only system) results in multiple histories which diverge at the moment of the change.
amboo7大约 4 年前
In simpler cases, you can see the problem as purely functional data structures.
评论 #26744535 未加载
评论 #26744337 未加载
jka大约 4 年前
Related to bitemporality, I&#x27;d be curious to hear whether anyone has experience with the Temporal Tables[1] extension in PostgreSQL?<p>[1] - <a href="https:&#x2F;&#x2F;github.com&#x2F;arkhipov&#x2F;temporal_tables" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;arkhipov&#x2F;temporal_tables</a>
评论 #26752355 未加载