SQLite VS Firebird

SQLite

• A SQLite extension that brings column-oriented tables to SQLite
  5 projects | news.ycombinator.com | 1 Feb 2024

  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
  1 project | news.ycombinator.com | 1 Nov 2023
• Ask HN: Where do I find good code to read?
  22 projects | news.ycombinator.com | 24 Aug 2023

  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
  8 projects | news.ycombinator.com | 13 Aug 2023

  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
  1 project | news.ycombinator.com | 27 Jul 2023

  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)
  7 projects | news.ycombinator.com | 12 Jun 2023
• SQLite builds for WASI since 3.41.0
  5 projects | news.ycombinator.com | 24 May 2023
• SQLite VS sqlite_blaster - a user suggested alternative
  2 projects | 17 Mar 2023
• Stop Saying “Technical Debt”
  1 project | news.ycombinator.com | 27 Feb 2023

  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

• Ce aplicație v-ar plăcea să o studiați code related?
  1 project | /r/programare | 16 Jan 2023

Firebird

We haven't tracked posts mentioning Firebird yet.
Tracking mentions began in Dec 2020.