support indexes on non-string types
Bug #987412 reported by
Eric Casteleijn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
U1DB |
Fix Released
|
Wishlist
|
Eric Casteleijn |
Bug Description
It would be nice to have indexes on the simple non-string types that are supported in json, at the very least booleans and integers.
Related branches
lp:~thisfred/u1db/number-mapping
- John A Meinel (community): Approve
-
Diff: 764 lines (+444/-151)6 files modifiedinclude/u1db/u1db.h (+5/-0)
setup.py (+1/-1)
src/u1db_query.c (+327/-145)
u1db/query_parser.py (+38/-3)
u1db/tests/test_backends.py (+16/-2)
u1db/tests/test_query_parser.py (+57/-0)
lp:~thisfred/u1db/index-booleans
- John A Meinel (community): Approve
- Diff: 0 lines
Changed in u1db: | |
status: | Triaged → In Progress |
Changed in u1db: | |
status: | In Progress → Fix Committed |
Changed in u1db: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The only way I see this working in the backend is a table per field type, but since json of course doesn't enforce that a field is the same type every time, we'll need a lot of error checking.