Comment by aerzen
2 days ago
Ok, hear me out: what if we make something that takes a postgres database dir, tars it together and encodes it as a binary blob in SQLite?
We could have SQLite within postgres within sqlite within postgres! Is it practical or even slightly useful? Of course not - but it's SQL databases all the way down. Not that this is a good thing in itself.
No need for `tar`, there is "SQLite Archive" https://www.sqlite.org/sqlar.html
Take it one step further, the table-oriented database(tm) , embed clickhouse, MongoDB, Redis and PostgreSQL to ensure you have more flexibility than anyone can utilize efficiently. The one database to rule them all.
Now you only need support for qcow columns which you can mount in your embedded engines....et volia, enjoy your storage and compute separation.
This is some kind of RDBMS mutant CRUDucken.
‘Tis the season.
“We need to go deeper” (https://i.kym-cdn.com/photos/images/newsfeed/000/384/176/d2f...)
My next project
next stop: mongodb inside sqlite inside postgresql
Giving @Transactional(NESTED) a whole new meaning.