Hi all,

In the table model, we planned to not support query sql without any
measurement columns in the select clause, if so, we will return an empty
result set, just like InfluxDB(1.X and 2.X).

For example, assuming that we have a table named `table1` and it has the
following data:

|time | device_id | s1| s2|
|------|---------------|----|----|
|     1|              d1|   1|   2|
|------|---------------|----|----|

If the query sql is `select time, device_id from table1`, currently we may
get an empty result set. This is strange because there does exist one row
in this table.

Even if we write the rule in documents, some users who are accustomed to
standard SQL may feel confused if they do not read the documentation
carefully.

So, I want to support this feature, to allow query sql without any
measurement columns in the select clause.

+1 for supporting query sql without any measurement columns in the select
clause
-1 for maintaining the status quo.



Best regards,
--------------------------
Yuan Tian

Reply via email to