boolif-postgresql
sqlite_fdw
| boolif-postgresql | sqlite_fdw | |
|---|---|---|
| 1 | 6 | |
| 0 | 195 | |
| - | 2.1% | |
| 0.0 | 5.7 | |
| over 2 years ago | 4 days ago | |
| PLpgSQL | PLpgSQL | |
| - | 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.
boolif-postgresql
-
PGSQL function: nik_boolif(true, true, 'It works!') returns 'It works!'
Get it here: https://github.com/brsnik/nik_boolif
sqlite_fdw
-
Things that surprised me while running SQLite in production
https://github.com/pgspider/sqlite_fdw
Postgres has foreign data wrappers which can kinda achieve this(see also: https://github.com/pgspider/sqlite_fdw ), but ive been surprised by how well sqlite is already supported by many tools : sometimes it comes for free as its used in testing - hooking up stuff like litestream can work really wel l too
-
Is it possible to import or convert an SQLite3 db file into a Postgres database on docker?
Another option might be the SQLite FDW
- Silver Bullet - Personal Knowledge Management
-
Fly.io Buys Litestream
I've not done this but it's intriguing; potentially a best-of-all-worlds solution.
I think "proper" automatic replication is not possible given the mismatch between Postgres and SQLite - not everything in Postgres maps to a thing that is possible in Postgres.
That said, there are a variety of ways to get data out of Postgres, and a variety of ways to get things into SQLite.
You could periodically export CSVs or whatever from Postgres and periodically import them into SQLite.
Or you could do a more realtime sync by using a Postgres foreign data wrapper like this one: https://github.com/pgspider/sqlite_fdw which would let you write directly to SQLite. Combine that with database triggers on the Postgres side of things and you've got something pretty close to realtime replication.
Those sorts of solutions wouldn't be as robust as "real" replication, but could be very useful for a lot of scenarios. You could have Postgres importing gobs of data, and "replicating" it over to your reporting server which uses SQLite as a data source.
-
How to load sqlite3 db file in pgadmin4?
pgadmin4 does not support it, but you can try sqlite_fdw
-
Which database should I use to store about 200GB of financial data?
If you encounter limitations posed by SQLite it will be easy to migrate to PostgreSQL. You can even open the SQLite database in PostgreSQL.
What are some alternatives?
parquet_s3_fdw - ParquetS3 Foreign Data Wrapper for PostgresSQL
chiselstore - SQLite + Little Raft = 🚀
rqlite - The lightweight, distributed relational database built on SQLite.
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
awesome-selfhosted - A list of Free Software network services and web applications which can be hosted on your own servers
honeysql - Turn Clojure data structures into SQL
better-sqlite3 - The fastest and simplest library for SQLite3 in Node.js.
silverbullet - The hackable notebook
rapid-cg - Rapid Application Development Code Generators
litestream - Streaming replication for SQLite.
litestream-base - A base Docker image for adding Litestream to apps
Bedrock - Rock solid distributed database specializing in active/active automatic failover and WAN replication