temporal_tables
rust_sqlite
Our great sponsors
temporal_tables | rust_sqlite | |
---|---|---|
16 | 9 | |
897 | 1,058 | |
- | - | |
4.2 | 0.0 | |
2 months ago | almost 2 years ago | |
C | Rust | |
BSD 2-clause "Simplified" License | 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
-
All the ways to capture changes in Postgres
There is also the temporal_tables extension.
[0] https://github.com/arkhipov/temporal_tables
-
Show HN: I made a CMS that uses Git to store your data
- https://github.com/arkhipov/temporal_tables
I haven't used any of these but I work on https://xtdb.com which is also implementing SQL:2011's temporal features :)
-
Data point versioning infrastructure for time traveling to a precise point in time?
It seems like PG has this extension here anyone ever use it?
-
Questions about history table pattern
You could look at that or ask me questions about it (disclaimer, I am the author). Also there is https://github.com/arkhipov/temporal_tables/
- Modern solutions for database auditing?
- How Postgres Audit Tables Saved Us from Taking Down Production
-
spring-data-jpa-temporal: a lightweight temporal auditing library
All good. Note there is also https://github.com/arkhipov/temporal_tables/ (which is also type 4 as a postgres extension - pretty similar to what ebean orm is doing)
-
Time-travel options for databases
The Temporal Tables Postgres extension works well. https://github.com/arkhipov/temporal_tables
-
easy master<->master postgresql 11 cluster solution?
If you're doing this across regions, you really really should reconsider. If you're doing it in the same data center you might be able to get away with it (but then I'm not sure why you're doing it in the first place, if the system fits in one DC then you probably can just scale up). It might be worth considering a sharded & passively combined approach -- i.e. every country has it's own data, and there's some huge public schema which consists of all the data that is drip fed in to materialized views or tables at regular intervals. You could also combine this with temporal_tables to get a very delayed but theoretically time-consistent (well, aside from clock skew across regions of course...) view of your DB to query... Really depends on the use case.
-
SQLite the only database you will ever need in most cases
One of postgres's most underrated features. RLS is amazing, can be unseen/basically work silently if your programming language-side tools are good enough, and is documented well (like everything else):
https://www.postgresql.org/docs/current/ddl-rowsecurity.html
But the power of PG is that it doesn't stop there, if you combine this with a plugin like temporal_tables and you can segment by user and time:
https://github.com/arkhipov/temporal_tables
All of this mostly unknown to the thing that's accessing the DB. If that's not enough for you, why not add some auditing with pgaudit:
https://www.pgaudit.org/#section_three
I think it might not actually be hyperbole to say that Postgres is the greatest RDBMS database that has ever existed.
rust_sqlite
- Writing a SQLite clone from scratch in C
- SQLite the only database you will ever need in most cases
- SQLRite – SQLite clone from scratch in Rust
-
What would SQLite look like if written in Rust? — Part 2
You may have noticed that throughout the entire code I am making reference to a SQLRiteError type. That is an error type I defined as an enum using the thiserror crate, that is a super easy to use library that provides a convenient derive macro for the standard library’s std::error::Error trait. If you check the commits in the github repository, you may notice that I first wrote my own implementation of the std::error::Error trait. But then I bumped into this trait, that basically takes care of a lot of the boiler plate, and let’s face it, the code looks super clean! This is our error module so far, located in src/error.rs .
-
New chapter on the series - Writing a SQLite clone from scratch in Rust
Also check out the github repo: https://github.com/joaoh82/rust_sqlite
- What would SQLite would look like if written in Rust?
- SQLite Clone from Scratch in Rust
-
What would SQLite look like if written in Rust? — Part 1
I assume that if you are trying to follow this and writing some code along with me you can manage to create an empty Rust project on your own. Just to be clear this is what I did to start: cargo new rust_sqlite --bin . But again, you can find all the code on Github.
-
What would SQLite look like if written in Rust? — Part 0
View on Github (pull requests are welcome)
What are some alternatives?
TimescaleDB - An open-source time-series SQL database optimized for fast ingest and complex queries. Packaged as a PostgreSQL extension.
sqlcipher - SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features.
pg_bitemporal - Bitemporal tables in Postgres
rustyline - Readline Implementation in Rust
pgaudit - PostgreSQL Audit Extension
medium-unlimited - A browser extension to read medium.com articles for free without membership.
dolt - Dolt – Git for Data
llvm-cbe - resurrected LLVM "C Backend", with improvements
datasette - An open source multi-tool for exploring and publishing data
rqlite - The lightweight, distributed relational database built on SQLite.
beekeeper-studio - Modern and easy to use SQL client for MySQL, Postgres, SQLite, SQL Server, and more. Linux, MacOS, and Windows.
chiselstrike - ChiselStrike abstracts common backends components like databases and message queues, and let you drive them from a convenient TypeScript business logic layer