Skip to content
ParticleDB
Release candidateParticleDB 1.1.19-rc.17 is not yet GA or ready for production data.Release status →

Historical reads

Historical queries require a server configuration that explicitly supports them. Ordinary durability and transaction isolation do not imply that older versions are queryable.

Check the installed server’s start --help for time-travel options. Verify retention, timestamp format, schema-change behavior and persistence across restarts using your release.

A historical query must fail clearly when the requested history is unavailable. Do not treat an empty result as proof that no records existed at that time.

For application audit history, maintain explicit event or change records with stable identifiers and timestamps. Keep that design separate from the database’s crash-recovery mechanism.

Transactions · Durability · Feature availability

Documentation home · Troubleshooting