junco-cms
pg_bitemporal
| junco-cms | pg_bitemporal | |
|---|---|---|
| 1 | 7 | |
| 9 | 140 | |
| - | 1.4% | |
| 3.5 | 0.0 | |
| about 1 year ago | about 2 years ago | |
| JavaScript | PLpgSQL | |
| MIT 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.
junco-cms
-
Show HN: I made a CMS that uses Git to store your data
This sounds cool. We wrote a git-based CMS[0] that is a little different. It has a nice-enough UI for creating and editing markdown documents, which are stored in git. And then it has a JSON API so that your main site can fetch the content and style / format however it likes. Users log in with OAuth or local passwords and their edits end up as git commits that are attributed to them.
[0]: https://github.com/frameable/junco-cms
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?
wasmer.io - The Wasmer.io website
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.
Publii - The most intuitive Static Site CMS designed for SEO-optimized and privacy-focused websites.
crux - General purpose bitemporal database for SQL, Datalog & graph queries. Backed by @juxt [Moved to: https://github.com/xtdb/xtdb]
Kirby - Kirby's core application folder
decap-cms - A Git-based CMS for Static Site Generators
outstatic - Outstatic - A static CMS for Next.js
cms - The core Laravel CMS Composer package