[pangram]

A few more features would make it useful for prototyping. The README says that it uses indexes to speed up queries, but it doesn't, at least not in current HEAD (05786eada4); it always queries all the records. It would be nice if it allowed comparisons on relationships other than just equality; for example, >, <, and "LIKE." Ideally, it would also handle handle nested structures.

[StavrosK]

Hah, I just posted this comment two seconds ago:

http://news.ycombinator.com/item?id=3599633

I pushed the README before the indexing code, but it's coming by next week. I'm also planning to have other operators, as you suggest (basically, anything SQLite allows will be allowed).

Nested structures will take a bit more work, but I don't see why they shouldn't be possible (the index would just look like "mydict.somekey" rather than "mydict").

I'd like to keep the project small, but I don't see the above changes taking a lot of code. The index creation code is just 7 more lines.

[pangram]

Fair enough. Might I suggest you put a comment to the effect of "indexes are a work in progress" in the README for now? Would help users that just run into it on Github randomly.

[StavrosK]

I have pushed the index code, now it uses the best available index for each query. I will need to test it more extensively, though.

[StavrosK]

I will do that now.