sqltorrent
alasql
| sqltorrent | alasql | |
|---|---|---|
| 5 | 4 | |
| 269 | 6,895 | |
| 1.1% | 0.6% | |
| 0.0 | 9.0 | |
| about 8 years ago | 2 days ago | |
| C | JavaScript | |
| Apache License 2.0 | 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.
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...
alasql
- AlaSQL Db for Browser and Node
- Alasql.js – JavaScript SQL database for browser and Node.js
- Let's write a compiler, part 5: A code generator
-
Hosting SQLite databases on GitHub Pages (or any static file hoster)
For similar results, you can use SQL with IndexedDB running fully client-side: https://github.com/agershun/alasql
What are some alternatives?
sql.js-httpvfs - Hosting read-only SQLite databases on static file hosters like Github Pages
torrent-net - Distributed search engines using BitTorrent and SQLite
sqlparse - A non-validating SQL parser module for Python
ipfs - Peer-to-peer hypermedia protocol
zetasql - ZetaSQL - Analyzer Framework for SQL
datasette - An open source multi-tool for exploring and publishing data
go-mysql-server - A MySQL-compatible relational database with a storage agnostic query engine. Implemented in pure Go.
IPSQL - InterPlanetary SQL
JSqlParser - JSqlParser parses an SQL statement and translate it into a hierarchy of Java classes. The generated hierarchy can be navigated using the Visitor Pattern
apsw - Another Python SQLite wrapper