get_range_from_index should raise a helpful exception when it gets invalid key values.
Bug #1020687 reported by
Eric Casteleijn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
U1DB |
Confirmed
|
Low
|
Unassigned |
Bug Description
A user tried to do this:
.get_range_
under the impression that passing None would mean an open ended range for the second field in the index, which does not work. We should raise an error in this case, informing the user that None is not a valid value for an index field.
Changed in u1db: | |
assignee: | Eric Casteleijn (thisfred) → nobody |
To post a comment you must log in.