Open eszter137 opened 5 years ago
@gabor1 Do you want to support when you have "{value}{operator}{key}" or you want to catch the error? We would have a more complex parser for recognising what "0.01>E_CC_MP2_2B" means at all?
well binary operators like that work both ways in any programming language, so it would be strange not to support that, no?
No, it is more like a filter where you have syntax like: {labels} {operators} {values}. Like in a dictionary you have a specific structure (keys and values) and you cannot switch the order. I mean in special cases you can but that will be a completly different object.
In the case of the programing language, it is easier because you can evaluate the whole expression.
Here have to figure out which one is the label: "0.01" or "E_CC_MP2_2B":
atoms.info["0.01"] > "E_CC_MP2_2B"
vs
atoms.info["E_CC_MP2_2B"] < 0.01
fine. we'll call it an enhancement
and so push it down the priority list ;-)
To implement this issue there could cause a big performance decrease because we have to handle all labels in the query as a regex. I would estimate feature needs more than 2 weeks to implement it properly.
This was discussed, and we decided that once strings values are indicated with quotes, it should be no problem to have either order around a binary operator.
The problem is with the ordering of the relation in the above query;
-q "E_CC_MP2_2B<0.01"
would work. Current error message: