Refactoring-Summary
SQLite
Refactoring-Summary | SQLite | |
---|---|---|
2 | 40 | |
684 | 5,575 | |
- | - | |
0.0 | 0.0 | |
over 1 year ago | 5 days ago | |
C | ||
- | 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.
Refactoring-Summary
-
Ask HN: Where do I find good code to read?
I find that reading books rather than code tends to be more helpful in terms of finding good takes on what clean code is -- more specifically books on refactoring or specific language-related features (like 'Effective Java' or 'Fluent Python'). The issue with just reading code is that many times - you'll miss out on why the author chose to use the expression or abstractions which they chose to use. Reading a book at least takes you through author's thought process. For an alternative - you could always browse repositories which contain notes on refactoring as well like this one (which does a good job summarizing some of the key principles from Fowler's book on refactoring):
https://github.com/HugoMatilla/Refactoring-Summary
-
Is it okay to return my original List/Collection/Datastructure I'm storing my data in or is that against some OOP principals?
https://github.com/HugoMatilla/Refactoring-Summary#28-encapsulate-collection
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?
glib - Read-only mirror of https://gitlab.gnome.org/GNOME/glib
sqlcipher - SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features.
sqlite - sqlite mirror
LevelDB - LevelDB is a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values.
clara-rules - Forward-chaining rules in Clojure(Script)
RocksDB - A library that provides an embeddable, persistent key-value store for fast storage.
retlang
sqlite_orm - ❤️ SQLite ORM light header only library for modern C++
pocket - Official implementation of the Pocket Network Protocol v1
bolt
beanie - Asynchronous Python ODM for MongoDB
phpMyAdmin - A web interface for MySQL and MariaDB