periods
pg_bitemporal
| periods | pg_bitemporal | |
|---|---|---|
| 5 | 7 | |
| 236 | 140 | |
| - | 1.4% | |
| 2.4 | 0.0 | |
| 3 months ago | about 2 years ago | |
| PLpgSQL | PLpgSQL | |
| PostgreSQL License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
periods
- Show HN: I made a CMS that uses Git to store your data
- Databases in 2021: A Year in Review
-
Status of WITH SYSTEM VERSIONING: need help understanding commitfest page
One of the first items in the linked thread also mentions an extension that does the same right now. https://github.com/xocolatl/periods/
-
Temporal tables patch in progress perhaps for PG 15
Found within the discussion is this postgresql extension which performs a similar role using triggers and stored procedures.
- Temporal Tables PostgreSQL Extension
pg_bitemporal
-
The Guide to PostgreSQL Data Change Tracking
I feel like i keep yelling the following, but bitemporal tables.
- https://aiven.io/blog/two-dimensional-time-with-bitemporal-d...
- https://github.com/scalegenius/pg_bitemporal
4 timestamps and some ugly queries.
-
Eventual Business Consistency
People here may also be interested to see this analysis of the state of SQL:2011 "temporal table" feature adoption: https://illuminatedcomputing.com/posts/2019/08/sql2011-surve...
I don't think much has really changed since, and I'm not sure Postgres is any closer to addressing this natively (although there have been extensions, e.g. https://github.com/scalegenius/pg_bitemporal).
- Show HN: I made a CMS that uses Git to store your data
-
Record history / Temporal table question
Something more sophisticated would be https://github.com/scalegenius/pg_bitemporal
- PostgreSQL 14 Released
-
Bitemporal History
Sure, I can appreciate that native support for a feature like this is nice.
As I understand it, most implementations (including another one for bitemporality[1]) involve either audit tables, as you mention, and/or additional support columns. It's as if the "now" representation is simply a narrow lens onto the underlying data.
That said, PostgreSQL encodes and has battle-tested decades of database functionality including an ecosystem around those, so I'd be a little wary of switching technology even if it does solve one individual problem thoroughly. Everything has to start somewhere, though.
[1] - https://github.com/scalegenius/pg_bitemporal
What are some alternatives?
zombodb - Making Postgres and Elasticsearch work together like it's 2023
temporal_tables - Temporal Tables PostgreSQL Extension
django-simple-history - Store model history and view/revert changes from admin site.
Reladomo - Reladomo is an enterprise grade object-relational mapping framework for Java.
pg_partman - Partition management extension for PostgreSQL
crux - General purpose bitemporal database for SQL, Datalog & graph queries. Backed by @juxt [Moved to: https://github.com/xtdb/xtdb]
wasmer.io - The Wasmer.io website
postgres-aws-s3 - aws_s3 postgres extension to import/export data from/to s3 (compatible with aws_s3 extension on AWS RDS)
outstatic - Outstatic - A static CMS for Next.js
clickhouse-operator - Altinity Kubernetes Operator for ClickHouse creates, configures and manages ClickHouse clusters running on Kubernetes
Kirby - Kirby's core application folder