Stoolap 0.5.0: One Query, One Answer
Comments on “Stoolap 0.5.0: One Query, One Answer”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Stoolap 0.5.0, an embedded SQL database, is aimed at making a query return the same answer on every internal path. Author Semih Alev shows 0.4.2 returning different results depending on an index, a checkpoint, or one corrupted byte that left a table empty without an error. The release centralizes comparison, ordering and arithmetic rules, turns runtime errors into failures, and adds V5 per-block checksums. It is not backward compatible on disk. The bug counts and benchmark figures are the author's own and have no independent source.
Why it ranked
No. 17 of 144 with a score of 0.65. The panel rated it highest on new information (0.92) and technical depth (0.91), lowest on audience breadth (0.42). Placed No. 17, No. 35 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Detailed engineering writeup of a database engine release with concrete reproducible wrong-answer examples and tests; substantive and technical, but niche to database builders and largely a release announcement.
- AI judgeJudge 3gpt-5.6-luna
- A deeply substantiated database release write-up with reproducible failure cases, semantic unification, corruption handling, recovery fixes, planner changes, tests, and performance measurements. It is highly actionable, though primarily relevant to database and systems builders.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.65total under rubric v2.3
- Significance0.58
- Reader interest0.78
- Audience breadth0.42
- Practical relevance0.72
- Substantiated0.89
- Technical depth0.91
- New information0.92
- Counts against: Promotional0.09
- Counts against: Overclaim0.20
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.66 | 0.35 | 0.72 | 0.58 | 0.37 | +0.24 | +0.138 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.81 | 0.60 | 0.92 | 0.78 | 0.32 | +0.26 | +0.202 |
| Audience breadthHow many people who build technology does it concern? | 0.40 | 0.30 | 0.55 | 0.42 | 0.25 | +0.13 | +0.054 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.75 | 0.60 | 0.82 | 0.72 | 0.22 | +0.22 | +0.159 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.95 | 0.80 | 0.93 | 0.89 | 0.15 | +0.05 | +0.045 |
| Technical depthHow technically substantive is it? | 0.97 | 0.85 | 0.91 | 0.91 | 0.12 | +0.05 | +0.046 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.87 | 0.90 | 0.99 | 0.92 | 0.12 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.05 | 0.15 | 0.08 | 0.09 | 0.10 | −0.19 | −0.018 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.21 | 0.30 | 0.08 | 0.20 | 0.22 | −0.11 | −0.022 |
| Sum of contributions | +0.650 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.650 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-19/17/"><img src="https://rubric.hrih.si/badge/2026-11-19/17.svg" alt="Ranked #17 on Rubric, 19 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 2 matches source · 6 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceNumber
Stoolap 0.5.0 includes 670 merged pull requests since 0.4.2, 182 closed issues, and a test suite that grew from 6,032 to 8,580 tests.
The cited source says the same thing.
The article says “670 merged pull requests since 0.4.2, 182 closed issues, and a test suite that grew from 6,032 to 8,580 tests”
The source says “670 merged pull requests since v0.4.2, 182 closed issues, 1,293 files changed (+275k / -96k lines), and the test suite grown from 6,032 to 8,580 tests”
Source cited by the article: github.com/stoolap/stoolap/releases/tag/v0.5.0
No source givenCausal conclusion
In Stoolap 0.4.2, a query with an IN list returned the matching row twice once an index existed, while 0.5.0 returns one row both times.
The article gives no link or citation for it.
The article says “With the index, the list was answered by probing the index once per member, and nothing removed a row that two members found”
The source says No source to compare with.
No source givenCausal conclusion
In 0.4.2, a single flipped byte in a volume file made the engine skip the file with a warning and return 0 rows with no error to the application.
The article gives no link or citation for it.
The article says “The engine then skipped the file, printed a warning to stderr and answered from what was left, which was nothing. No error reached the application”
The source says No source to compare with.
No source givenNumber
A test over generated statements found 282 wrong result cells in comparing a number with a TEXT before the rule was unified.
The article gives no link or citation for it.
The article says “A test over generated statements found 282 wrong result cells before the rule was unified”
The source says No source to compare with.
No source givenNumber
ORDER BY an alias answered wrong in 448 of 1,270 generated cases in 0.4.2.
The article gives no link or citation for it.
The article says “ORDER BY an alias answered wrong in 448 of 1,270 generated cases”
The source says No source to compare with.
No source givenNumber
In 0.4.2, i64::MIN / -1 crashed the process and ABS(i64::MIN) returned NULL.
The article gives no link or citation for it.
The article says “In 0.4.2, i64::MIN / -1 crashed the process and ABS(i64::MIN) returned NULL”
The source says No source to compare with.
Matches sourceVersion
Stoolap 0.5.0 writes volumes in a new V5 format in which every column block and metadata section has its own CRC-32C, and 0.4.2 cannot open a database once 0.5.0 has written a manifest.
The cited source says the same thing.
The article says “Once 0.5.0 has written a manifest, 0.4.2 cannot open the database”
The source says “Volume files (vol_*.vol) | V4 | V5, with a CRC-32C on every section and block”
Source cited by the article: stoolap.io/docs/development/migration-v042-to-v050
No source givenNumber
A primary-key SELECT inside an explicit transaction went from about 800 ns and 36 allocations to about 180 ns and 5 allocations.
The article gives no link or citation for it.
The article says “about 800 ns and 36 allocations before, about 180 ns and 5 now”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 19 Nov 2026, 05:47 UTC. It played no part in the ranking.