temporal_tables
Logidze
Our great sponsors
| temporal_tables | Logidze | |
|---|---|---|
| 6 | 6 | |
| 576 | 1,556 | |
| 4.0% | - | |
| 4.9 | 5.5 | |
| 5 months ago | about 2 months ago | |
| PLpgSQL | Ruby | |
| GNU General Public License v3.0 or later | MIT 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.
temporal_tables
- PostgreSQL temporal_tables extension in PL/pgSQL
-
Versioning data in Postgres? Testing a Git like approach
It was reimplemented in pure SQL here https://github.com/nearform/temporal_tables for this purpose
-
All the ways to capture changes in Postgres
I enjoyed this blog. I think it provides a great succinct overview of various approaches native to Postgres.
For the "capture changes in an audit table" section, I've had good experiences at a previous company with the Temporal Tables pattern. Unlike other major RDBMS vendors, it's not built into Postgres itself, but there's a simple pattern [1] you can leverage with a SQL function.
This allows you to see a table's state as of a specific point in time. Some sample use cases:
- "What was this user's configuration on Aug 12?"
- "How many records were unprocessed at 11:55pm last night?"
- "Show me the diff on feature flags between now and a week ago"
[1]: https://github.com/nearform/temporal_tables
-
Show HN: I made a CMS that uses Git to store your data
One of these Postgres-based implementations of SQL:2011's temporal versioning features might get you close enough:
- https://github.com/nearform/temporal_tables
-
How to implement row changes history?
You don't really need to install an extension to use temporal tables, there is an alternative (https://github.com/nearform/temporal_tables) implemented purely as a plpgsql trigger so that it works everywhere.
-
Temporal Tables PostgreSQL Extension
I was part of a team at NearForm using this for a project on an EC2 instance. In order to move to AWS RDS we had to recreate the functionality of temporal_tables as a PostgreSQL function, rather than extension.
When we switched, we found that although there were minor bugs, we didn't have any noticeable loss of performance and we have used it ever since for many projects.
https://github.com/nearform/temporal_tables
If you're also limited by cloud services and the extensions limitations, this is a great solution.
Logidze
-
Versioning data in Postgres? Testing a Git like approach
There's an interesting approach to it that works with Rails and PostgreSQL using triggers.
https://github.com/palkan/logidze
- Database changes log for Rails
-
Best rails tools to automatically handle logging of things like all a user's actions, or changes to a record in a module - primarily for audit purposes.
https://github.com/palkan/logidze is my favorite for these kind of things
-
How would you build an audit log in Rails for a high-throughput API?
Have you considered https://github.com/palkan/logidze ?
- Temporality/time-travelling in DB with ActiveRecord?
-
Is it a terrible idea to manually create a table in a MySQL database generated by a rails model?
Something like this might be an option? https://github.com/palkan/logidze
What are some alternatives?
temporal_tables - Temporal Tables PostgreSQL Extension
PaperTrail - Track changes to your rails models
pgkit - Pgkit - Backup, PITR and recovery management made easy
Audited - Audited (formerly acts_as_audited) is an ORM extension that logs all changes to your Rails models.
walex - Postgres change events (CDC) in Elixir
marginalia - Attach comments to ActiveRecord's SQL queries
pg-event-proxy-example - Send NOTIFY and WAL events from PostgreSQL to upstream services (amqp / redis / mqtt)
Destroyed At - ActiveRecord Mixin for Safe Destroys
maxwell - Maxwell's daemon, a mysql-to-json kafka producer
rails_or - Cleaner syntax for writing OR Query in Rails 5, 6. And also add #or support to Rails 3 and 4.
connectors - Connectors for capturing data from external data sources
Paranoia - acts_as_paranoid for Rails 5, 6 and 7