squirrelbyte
rust_sqlite
| squirrelbyte | rust_sqlite | |
|---|---|---|
| 3 | 9 | |
| 135 | 1,058 | |
| - | - | |
| 0.0 | 0.0 | |
| almost 3 years ago | almost 2 years ago | |
| Go | Rust | |
| MIT License | 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.
squirrelbyte
- SQLite the only database you will ever need in most cases
-
HelloDB: Simple JSON database
Just saw a similar project posted the other day
- Show HN: Squirrelbyte – a SQLite-based JSON document server
rust_sqlite
- Writing a SQLite clone from scratch in C
- SQLite the only database you will ever need in most cases
- SQLRite – SQLite clone from scratch in Rust
-
What would SQLite look like if written in Rust? — Part 2
You may have noticed that throughout the entire code I am making reference to a SQLRiteError type. That is an error type I defined as an enum using the thiserror crate, that is a super easy to use library that provides a convenient derive macro for the standard library’s std::error::Error trait. If you check the commits in the github repository, you may notice that I first wrote my own implementation of the std::error::Error trait. But then I bumped into this trait, that basically takes care of a lot of the boiler plate, and let’s face it, the code looks super clean! This is our error module so far, located in src/error.rs .
-
New chapter on the series - Writing a SQLite clone from scratch in Rust
Also check out the github repo: https://github.com/joaoh82/rust_sqlite
- What would SQLite would look like if written in Rust?
- SQLite Clone from Scratch in Rust
-
What would SQLite look like if written in Rust? — Part 1
I assume that if you are trying to follow this and writing some code along with me you can manage to create an empty Rust project on your own. Just to be clear this is what I did to start: cargo new rust_sqlite --bin . But again, you can find all the code on Github.
-
What would SQLite look like if written in Rust? — Part 0
View on Github (pull requests are welcome)
What are some alternatives?
litestore - A lightweight, self-contained, RESTful, searchable, multi-format NoSQL document store.
sqlcipher - SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features.
temporal_tables - Temporal Tables PostgreSQL Extension
beekeeper-studio - Modern and easy to use SQL client for MySQL, Postgres, SQLite, SQL Server, and more. Linux, MacOS, and Windows.
rustyline - Readline Implementation in Rust
nrkbetaquiz - Require the reader to pass a quiz before being able to comment on an article
medium-unlimited - A browser extension to read medium.com articles for free without membership.
llvm-cbe - resurrected LLVM "C Backend", with improvements
dqlite - Embeddable, replicated and fault tolerant SQL engine. [Moved to: https://github.com/canonical/dqlite]
rqlite - The lightweight, distributed relational database built on SQLite.