Talk:Tkrzw
 | This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||
| |||||||||||||||||
.svg){kind=logo}
Mistake edit
Is there a mistake with respect to the numbers? If I want to have 50% filling at most, then 1 million records should be stored in a table with 2 million entries. 6 bytes per record would give a 12MByte table.
Dubious comparison to SQLite edit
and was a multithreaded embedded database manager, comparable in functionality to SQLite[1] (but without an actual SQL implementation)
Very little about this makes sense. SQLite is indeed an embedded database manager, but one that is aggressively single threadded. Saying that something is like SQLite, but multithreaded and lacking an actual SQL implementation is about as sensical as saying something is like an elephant, but bright pink, and tiny. Can anyone get ahold of the cited source to see if there's anything to this claim? PiAndWhippedCream (talk) 21:08, 20 January 2015 (UTC)
- It's pretty much straight from the source, IIRC. In any case, both are libraries that manage databases stored as simple files, implement hash tables and B+ trees and have a C API for manipulating databases. (I would personally say Berkeley DB is more similar, but I've gone with what the sources say.) QVVERTYVS (hm?) 17:41, 21 January 2015 (UTC)