Hi,
Good catch, in previous `without null any/all`, any stands for
`and`(your choice 1); all stands for `or`(your choice 2);
I think in our having clause, we can keep consistent with where
clause. In our where clause, if you write select s1 from root.sg.*
where s1 > 1, we will write it as select
This is really a good feature!
Unlike relational database query, the 'column' name in IoTDB is a string
concatenated by the prefix path in FROM clause and the suffix path in SELECT
clause. In some cases maybe there are more than 1 output columns. If so, does
one simple HAVING clause still work
Hello everyone,
We want to support having clause in IoTDB.
1.Background
Replace grammar ‘without null any/all()’ to help users easier to understand and
use.
2.Specification
2.1Current query grammar
selectStatement
: TRACING? selectClause intoClause? fromClause whereClause? specialClause?
