You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> select * from thing
name: thing
-----------
time value
1970-01-01T00:15:00Z 50
1970-01-01T00:15:10Z 60
Now it gets weird. This returns nothing, although it should at least return the first point
> select * from thing where time <= 900s
Now without the units, and it returns both points. Timestamp should be nanoseconds by default, but it doesn't matter what I use in the comparison, it always returns both points:
> select * from thing where time <= 900
name: thing
-----------
time value
1970-01-01T00:15:00Z 50
1970-01-01T00:15:10Z 60
> select * from thing where time <= 9
name: thing
-----------
time value
1970-01-01T00:15:00Z 50
1970-01-01T00:15:10Z 60
> select * from thing where time = 9
name: thing
-----------
time value
1970-01-01T00:15:00Z 50
1970-01-01T00:15:10Z 60
> select * from thing where time = 9099099900999000990
name: thing
-----------
time value
1970-01-01T00:15:00Z 50
1970-01-01T00:15:10Z 60
Using explicit seconds for the time behaves as expected:
> select * from thing where time =900s
name: thing
-----------
time value
1970-01-01T00:15:00Z 50
> select * from thing where time = 910s
name: thing
-----------
time value
1970-01-01T00:15:10Z 60
> select * from thing where time = 911s
> select * from thing where time >= 911s
> select * from thing where time >= 900s
name: thing
-----------
time value
1970-01-01T00:15:00Z 50
1970-01-01T00:15:10Z 60
The text was updated successfully, but these errors were encountered:
There's something badly broken with comparison operators in the latest 0.9.3 nightly.
Insert two points with small epoch timestamps (in seconds):
Select the points in the CLI:
Now it gets weird. This returns nothing, although it should at least return the first point
Now without the units, and it returns both points. Timestamp should be nanoseconds by default, but it doesn't matter what I use in the comparison, it always returns both points:
Using explicit seconds for the time behaves as expected:
The text was updated successfully, but these errors were encountered: