-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange behavior with q and numbers #1258
Comments
ok, interesting! Might be I have never tested a negative floating point number ... Thanks for reporting!!! |
Hopefully fixed it. |
Hi Ken, Excellent reactivity and good job, we'll test it eventually. Did you also see the fact that the standard allows for numbers to be expressed with exponentials (I don't know if this is the right term), like 1.03E4 (for 1.03 times 10 to the power of 4)? I don't think Orion can do that or at least couldn't make it work. |
Yes, about that you're perfectly right. |
Maybe I can help. Stay tuned :) |
ok! :) |
Hello there,
and entity created with the field xy set to -1.03 is not returned by this query:
/entities?type=Temperature&q=xy==-1.03
If the entity is created with field set to a negative integer, this request works:
/entities?type=Temperature&q=xy==-103
Funny story, we pulled version 1.15.0-next and from what the debugger shows, it always goes into the QNodeIntegerValue case for negative numbers (line 184 of qLex.cpp).
Additionally, it seems impossible to specify numbers as in RFC 8259 (e.g. 103E-2).
The text was updated successfully, but these errors were encountered: