Hi, We get some astonishement with the current behavior of the client with the range search syntax.Currently: `Field: 1..42` will become `[('field', '>=', 1), ('field', '<', 42)]` But it seems people expect: `[('field', '>=', 1), ('field', '<=', 42)]` One point about the current behavior is that you can slide the range by the length and it will not contain any duplication. So what do you think?
It depends as it is displayed by the two questions in this stackoverflow post: https://english.stackexchange.com/questions/118402/when-is-between-inclusive-and-when-exclusive So I think it's a matter of convention and of context. The only way to be unambiguous would be to implement a different version of the .. operator: Field: ]1, 42] Field: [1, 42[ … But the parser might not allow it. -- Nicolas Évrard - B2CK SPRL E-mail/Jabber: nicolas.evr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
signature.asc
Description: Digital signature
