sql.js-httpvfs
sqltorrent
sql.js-httpvfs | sqltorrent | |
---|---|---|
15 | 5 | |
3,233 | 269 | |
- | 1.1% | |
1.5 | 0.0 | |
about 1 year ago | about 8 years ago | |
TypeScript | C | |
Apache License 2.0 | Apache License 2.0 |
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.
sql.js-httpvfs
-
A future for SQL on the web (2021)
I couldn't find do these wrappers support read-only SQLite databases with HTTP range requests, like in this famous post [1]. Phiresky's wrapper supports it, but it seems to be rebuilding the whole sql.js [2], I'd rather have it as VFS on top of sqlite.org's own WASM module. I like the idea of HTTP range requests, but I don't want to run a fork, that will be unmaintained in few years.
[1]: https://news.ycombinator.com/item?id=27016630
[2]: https://github.com/phiresky/sql.js-httpvfs
- Cloud Backed SQLite
-
Transmission 4.0.0 beta 1 is out
Oh that’s an interesting idea. I saw someone built SQLite over HTTP with the Range header: https://phiresky.github.io/blog/2021/hosting-sqlite-database...
So presumably in a similar manner as https://github.com/phiresky/sql.js-httpvfs you could map SQLite pages to leaf torrents too and get the chunking you are looking for.
-
netgrep - An experimental porting of ripgrep on WASM over the HTTP protocol.
But ripgrep has to read the whole file; if your intended use case is searching a blog, I'd recommend using something which makes an index, so you don't need to download everything. For example, sql.js-httpvfs is SQLite ported to wasm, with the DB file read over HTTP. If you use FTS to make an index, it works astonishingly well for text search.
-
Datasette Lite: a server-side Python web application running in a browser
How close is Python SQLite and Datasette Lite to accessing a hosted SQL database using HTTP range requests as can be done in sql.js like https://github.com/phiresky/sql.js-httpvfs?
I put together a Pyodide-based web app where users need a few indexed queries from a 600mb SQLite database but it isn't very practical for them to download the whole thing into the browser.
https://observablehq.com/@thadk/life
-
Ws4sqlite: Query SQLite via HTTP
You can also access sqlite databases directly from an http server that supports range requests (like s3). There are a bunch of implementations of this in different languages including Go[0] and Javascript[1].
[0]: https://github.com/psanford/sqlite3vfshttp
[1]: https://github.com/phiresky/sql.js-httpvfs
-
Static torrent website with peer-to-peer queries over BitTorrent on 2M records
Thanks to SQLite VFS abstraction, it is possible to implement your own file system on which SQLite parks data and structures. Inspired by Phiresky's sql.js-httpvfs which uses HTTP Range requests to lazy load blocks of storage from a static web server, I changed few lines of code to point the VFS read() calls to a database seeded by peers as a torrent. A 300 MiB db with 2 million records can be queried from seeders for full text searches in less than 2 MiB traffic with the BitTorrent protocol, all inside the browser, in a static website.
-
WebVM: Server-less x86 virtual machines in the browser
Hosting SQLite Databases on GitHub Pages" https://news.ycombinator.com/item?id=28021766 : DuckDB can query [and page] Parquet from GitHub, sql.js-httpvfs, sqltorrent, File System Access API (Chrome only so far; IDK about resource quotas and multi-GB datasets), serverless search with WASM workers
https://github.com/phiresky/sql.js-httpvfs :
> sql.js is a light wrapper around SQLite compiled with EMScripten for use in the browser (client-side).
> This repo is a fork of and wrapper around sql.js to provide a read-only HTTP-Range-request based virtual file system for SQLite. It allows hosting an SQLite database on a static file hoster and querying that database from the browser without fully downloading it.
> The virtual file system is an emscripten filesystem with some "smart" logic to accelerate fetching with virtual read heads that speed up when sequential data is fetched. It could also be useful to other applications, the code is in lazyFile.ts. It might also be useful to implement this lazy fetching as an SQLite VFS [*] since then SQLite could be compiled with e.g. WASI SDK without relying on all the emscripten OS emulation.
- Show HN: Link-Archive.org
-
Database-Less Torrent Website
It doesn't have to be range requests, you could split the file instead of depending on the range requests. Essentially it's the same as the chunking instructions for hosters who have a maximum file size as is demonstrated here: https://github.com/phiresky/sql.js-httpvfs/blob/master/creat...
sqltorrent
-
BTFS (BitTorrent Filesystem)
Or even better store data as an sqlite file that is full-text-search indexed. Then you can full-text search the torrent on demand: https://github.com/bittorrent/sqltorrent
- SQLite BitTorrent Vfs
-
How to circumvent Sci-Hub ISP block
"There was that project some guy posted a while back that used a combination of sqlite and partial downloads to enable searches on a database before it was downloaded all the way."
https://github.com/bittorrent/sqltorrent
- Hosting SQLite databases on GitHub Pages (or any static file hoster)
-
Distributed search engines using BitTorrent and SQLite
Interesting question. I looked at the source code to understand that.
SQLite knows where to look for when you open a SQLite database and you run a query, right? It just asks the underlying filesystem to provide N bytes starting from an offset using a C function, then it repeats the same operation on different portions of the file, it does its computation and everybody is happy.
The software relies on sqltorrent, which is a custom VFS for SQLite. That means that SQLite function to read data from a file stored in the filesystem is replaced by a custom function. Such custom code computes which Torrent block(s) should have the highest priority, by dividing the offset and the number of bytes that SQLite wants to read by the size of the torrent blocks. It is just a division.
See: https://github.com/bittorrent/sqltorrent/blob/master/sqltorr...
What are some alternatives?
alasql - AlaSQL.js - JavaScript SQL database for browser and Node.js. Handles both traditional relational tables and nested JSON data (NoSQL). Export, store, and import data from localStorage, IndexedDB, or Excel.
torrent-net - Distributed search engines using BitTorrent and SQLite
datasette - An open source multi-tool for exploring and publishing data
ipfs - Peer-to-peer hypermedia protocol
sqlite3vfshttp - Go sqlite3 http vfs: query sqlite databases over http with range headers
duckdb - DuckDB is an in-process SQL OLAP Database Management System
IPSQL - InterPlanetary SQL
wp-sqlite-db - A single file drop-in for using a SQLite database with WordPress. Based on the original SQLite Integration plugin.
apsw - Another Python SQLite wrapper
webvm - Virtual Machine for the Web
SkySQL