<p>A temporal database is one that gives you access to historical data, i.e., old data which would've otherwise been overwritten by new data, e.g. during an entity update. However, this is an incomplete picture, since temporality is often modelled at the schema level inside databases that are not intrinsically temporal.</p>
<p>For a deeper, more detailed excursion into the concept of temporality, see this post: </p>
<div class="embed-wrapper"><div class="embed-loading"><div class="loadingRow"></div><div class="loadingRow"></div></div><a class="embed-card" href="https://adityamukho.com/exploring-temporality-in-databases">https://adityamukho.com/exploring-temporality-in-databases</a></div>


A temporal database is one that gives you access to historical data, i.e., old data which would've otherwise been overwritten by new data, e.g. during an entity update. However, this is an incomplete picture, since temporality is often modelled at the schema level inside databases that are not intrinsically temporal.

For a deeper, more detailed excursion into the concept of temporality, see this post: 

%[https://adityamukho.com/exploring-temporality-in-databases]


What is a Temporal Database Anyway?

RecallGraph is a versioned-graph data store - it retains all changes that its data (vertices and edges) have gone through to reach their current state.
