pg_bitemporal
wasmer.io
pg_bitemporal | wasmer.io | |
---|---|---|
7 | 3 | |
140 | 22 | |
1.4% | - | |
0.0 | 6.3 | |
about 2 years ago | 11 months ago | |
PLpgSQL | JavaScript | |
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.
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
wasmer.io
-
Announcing WASIX - the Superset of WASI
The funny thing is that you can actually check for these things if you go beyond the shitposting, as all our work in the website is actually done in the open: https://github.com/wasmerio/wasmer.io (check the history for the pages, if you know how to code it should be easy to spot!)
-
Show HN: I made a CMS that uses Git to store your data
This is awesome. I was looking for something similar (either fully static or a headless CMS) for using it on the Wasmer website blog [1], which is already using Next.js.
We'll give it a try... thanks for the great work!
[1]: https://github.com/wasmerio/wasmer.io
-
WebAssembly as a Universal Binary Format – Part I: Native executables
The article lives here: https://github.com/wasmerio/wasmer.io/blob/master/_posts/wasm-as-universal-binary-format-part-1-native-executables.md
What are some alternatives?
temporal_tables - Temporal Tables PostgreSQL Extension
periods - PERIODs and SYSTEM VERSIONING for PostgreSQL
Reladomo - Reladomo is an enterprise grade object-relational mapping framework for Java.
junco-cms - Minimal git-based CMS in Node.js
crux - General purpose bitemporal database for SQL, Datalog & graph queries. Backed by @juxt [Moved to: https://github.com/xtdb/xtdb]
outstatic - Outstatic - A static CMS for Next.js
vscode-wasm - WebAssembly extension for VSCode
Kirby - Kirby's core application folder
temporal_tables - Postgresql temporal_tables extension in PL/pgSQL, without the need for external c extension.
Publii - The most intuitive Static Site CMS designed for SEO-optimized and privacy-focused websites.
sitepress - Sitepress ruby gems