ws4sqlite
SQLite
ws4sqlite | SQLite | |
---|---|---|
7 | 40 | |
390 | 5,537 | |
- | - | |
7.3 | 0.0 | |
2 days ago | 5 days ago | |
Go | C | |
ISC 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.
ws4sqlite
-
ws4sqlite v0.12.1 released - connect to sqlite via HTTP/"REST"
If you are interested, feel free to browse the git repo, read the documentation (with a tutorial) or connect to the discord channel.
-
Ask HN: Have you used SQLite as a primary database?
I am using sqlite where a simple persistence layer is needed, both as the sole in the project or along with a full-fledged database. There are many such projects, once you realize that a database is just an abstraction; for example, for caching in a larger project, or to store results for a subsection of the project. But of course also for smaller, standalone projects.
Also, take a look at ws4sqlite (https://germ.gitbook.io/ws4sqlite/) for a middle ground between SQLite (embedded) and rqlite/dqlite: it's "normal" sqlite addressable via web services. May be useful in some scenarios.
-
Hacker News top posts: Mar 11, 2022
Ws4sqlite: Query SQLite via HTTP\ (30 comments)
- Ws4sqlite: Query SQLite via HTTP
-
A remote JSON interface for SQLite, in Go
ws4sqlite is a web service layer on one (or more) SQLite databases. It’s written in Go, over mattn's go-sqlite3, and allows to use HTTP POST requests to submit SQL statements to a database, in a transaction. It can “serve” multiple databases at once, supports authentication, “stored queries”, in-memory databases, maintenance (vacuum/backups), batching and several other security features and configurations.
SQLite
- Show HN: Roast my SQLite encryption at-rest
-
A SQLite extension that brings column-oriented tables to SQLite
If you are into alternative storage engines for SQLite, there is also an LSM (Log-Structured Merge-tree) extension in the main repository that is not announced nor documented but seems to work. It’s based on the SQLite 4 project.
https://github.com/sqlite/sqlite/tree/master/ext/lsm1
https://www.charlesleifer.com/blog/lsm-key-value-storage-in-...
- SQLite License
-
Ask HN: Where do I find good code to read?
The sqlite code base is really well done. Lots of documentation.
https://github.com/sqlite/sqlite
-
Show HN: I wrote a RDBMS (SQLite clone) from scratch in pure Python
Especially the VM part: https://github.com/spandanb/learndb-py/blob/master/learndb/v...
Compare it with this: https://github.com/sqlite/sqlite/blob/master/src/vdbe.c
That's said, I'm curious how complete this LearnDB is. SQLite is hard to read not only it's old but also it covers a lot of SQL and following SQL spec makes hings complicated. SQLite has great test suite so it's nice if you run the suit against this implementation.
-
SQLite Begin Concurrent
Correct, see the github mirror[1]. I don't know how well supported that feature is compared to main branch. If it was completely stable, then it would have already landed in the main stable branch. Clarity about the roadmap of that branch would be nice.
1. https://github.com/sqlite/sqlite/tree/begin-concurrent
- Why sqlite3 temp files were renamed 'etilqs_*' (2006)
- SQLite builds for WASI since 3.41.0
-
SQLite VS sqlite_blaster - a user suggested alternative
2 projects | 17 Mar 2023
-
Stop Saying “Technical Debt”
Including comprehensive comments, documentation and tests in a codebase takes time and effort.
Failing to do so creates code that is very difficult to maintain or for someone new to the codebase to understand.
However, time and effort may not be what the organization wants to pay for, and individuals may view their own incomprehensible code as something like job security, as they can't be replaced by someone else easily.
As an example of complicated code that's still well-documented, the open-source sqlite code is a good example, about 1/4 of the B-tree file is comments, every time a variable is defined there's a short note explaining what it's used for, every function has a comment header that's comprehensive, such that someone new to the codebase could construct a map of how it all works fairly quickly. It's a good model for how to avoid the problem:
https://github.com/sqlite/sqlite/blob/master/src/btree.c
What are some alternatives?
tuql - Automatically create a GraphQL server from a SQLite database or a SQL file
sqlcipher - SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features.
dashera - DasherA is a Data General DASHER D200/D210 terminal emulator
LevelDB - LevelDB is a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values.
Sqinn-Go - Golang SQLite without cgo
RocksDB - A library that provides an embeddable, persistent key-value store for fast storage.
sqlite-s3-query - Python functions to query SQLite files stored on S3
sqlite_orm - ❤️ SQLite ORM light header only library for modern C++
barrier - Open-source KVM software
bolt
sqlite3vfshttp - Go sqlite3 http vfs: query sqlite databases over http with range headers
phpMyAdmin - A web interface for MySQL and MariaDB