temporal_tables
sqlcipher
Our great sponsors
temporal_tables | sqlcipher | |
---|---|---|
16 | 9 | |
897 | 5,941 | |
- | 1.4% | |
4.2 | 7.6 | |
2 months ago | 4 days ago | |
C | C | |
BSD 2-clause "Simplified" License | GNU General Public License v3.0 or later |
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.
sqlcipher
-
Basic Security Practices for SQLite: Safeguarding Your Data
SQLite, while versatile and easy to use, does not include built-in support for encryption, leaving the data at rest potentially vulnerable. To address this, external tools such as the SQLite Encryption Extension (SEE) or open-source projects like SQLCipher can be employed to encrypt the database file. This process can be achieved through the following steps:
-
What is the best way to store data?
I am personally using SQLite for a project that has been ordered by some future clients and it would perfectly suit your case. I strongly recommend it. Moreover, you can encrypt your entire db is you use this.
-
Passkeys: The Beginning of the End of the Password
> Cloud sync (encrypted!) is important because your average user needs that convenience and durability of authenticator
Local-only iOS Codebook [1] sync (open-source encrypted! by SQLCipher [2]) provides convenience, durability, transparency, decentralization and fewer supply chain dependencies.
[1] https://www.zetetic.net/codebook
[2] https://github.com/sqlcipher/sqlcipher
-
Injecting (cryptographic) secrets into automated software release build pipelines?
One option that I have been considering is creating a simple, encrypted SQL database (like SQLite & SQLcipher combo), that could be used to store & retrieve crypto secrets required in the release build pipeline. To manipulate this database, one needs to provide a password. This solution could be implemented as a microservice running on the build server, for example, in a dedicated docker container. To trigger a new release build, the user with the correct credentials could access the build server over our local network, and, if in a possession of the correct password required to decrypt the crypto database, trigger a release build.
-
I made an app just to say F%$K to LastPass
That's not true. There are wonderful open source projects ensuring that layer. https://github.com/sqlcipher/sqlcipher for example.
-
Connecting to a sqlite database, but encrypting it at rest
No, SQLCipher takes another approach. They modify the source of SQLite's pager with numerous code blocks in order to "hook in" the encryption code. Compare this SQLCipher code to the original SQLite code.
- SQLite the only database you will ever need in most cases
-
Encrypted sqLite
Your options are use SQLCipher to transparently encrypt the entire DB file on the device, or your have your app handle the encryption/decryption of each record during each read/write operation. If AES-256 isn't a hard requirement, encrypting at the record level is way easier with libsodium secretbox
What are some alternatives?
TimescaleDB - An open-source time-series SQL database optimized for fast ingest and complex queries. Packaged as a PostgreSQL extension.
sqlitebrowser - Official home of the DB Browser for SQLite (DB4S) project. Previously known as "SQLite Database Browser" and "Database Browser for SQLite". Website at:
pg_bitemporal - Bitemporal tables in Postgres
SQLite - Official Git mirror of the SQLite source tree
pgaudit - PostgreSQL Audit Extension
rust_sqlite - SQLRite - Simple embedded database modeled off SQLite in Rust
dolt - Dolt – Git for Data
SQLite3MultipleCiphers - SQLite3 encryption extension with support for multiple ciphers
datasette - An open source multi-tool for exploring and publishing data
litestream - Streaming replication for SQLite.
beekeeper-studio - Modern and easy to use SQL client for MySQL, Postgres, SQLite, SQL Server, and more. Linux, MacOS, and Windows.
sql.js - A javascript library to run SQLite on the web.