How to store data when SQL sucks

Is SQLite the only option for data storage in a cross-platform desktop app? WTF?

SQL is such a broken leaky abstraction and most NoSQL stuff is even worse (JSON for queries? Seriously?). Either way though none of that helps desktop apps unless you want to manage a separate database process.

I'm tempted to write my own B+tree impl but that's like a pain in the ass. Where is libpersistent-data-structures that I can drop into my project?

or go on strike
chinamen
RAUGHING OUT ROUD

>>1 if you're too fucking stupid for eating horse manure just write it down on paper or speak it into your iphone faggot op

MDB is simpler, smaller, and faster than Berkeley DB. http://symas.com/mdb/microbench/

If you're writing sepples, consider boost::serialize and now you have two problems

UTF-8 text file. Far more efficent than your shitty SQL.

>>39
NO!

Think of chineses as memory pages. You can now sort them in any order (by name, by birth datetime, you name it, just watch out for collisions!) to obtain a chinese address space.

Then you just map your address space to the chinese address space. MAX_BYTES_TO_MEMORIZE_BY_A_CHINESE constant will be of help, but obtaining its value is left as an excercise for the reader.

>>45
Thing is MAX_BYTES_TO_MEMORIZE_BY_A_CHINESE is variable, though that increases complexity and depending on the amount of variance might not be worth the extra storage space. Further investigation is recommended.