Hi Abdelrahman:
I also vote for Option A.
Best regards,
Zhehan Chen
原始邮件
发件人:Yuan Tian <[email protected]>
发件时间:2026年3月27日 08:41
收件人:dev <[email protected]>
主题:Re: [VOTE] FROM-first syntax clause ordering
Hi Abdelrahman,
I would like to cast my vote for Option A (FROM relation SELECT WHERE).
My main reasons for preferring this option are:
- Consistency: It aligns with the approach used in DuckDB, which helps
maintain consistency and provides a more familiar experience for users
migrating from other systems.
- Ease of Adoption: Leveraging an existing implementation pattern can
reduce the learning curve for our users.
Best regards,
Yuan Tian
On Thu, Mar 26, 2026 at 5:32
PM Abdelrahman Mostafa <
[email protected]> wrote:
> Hi all,
>
> Following the discussion on adding FROM-first syntax support to IoTDB's
> Table SQL dialect, I would like to initiate a vote on the clause ordering.
>
> We currently have two options:
>
> Option A: (FROM relation SELECT WHERE)
>
> Example: FROM sensors SELECT temperature WHERE temperature > 15
>
> Option B: (FROM relation WHERE SELECT)
>
> Example: FROM sensors WHERE temperature > 15 SELECT temperature
>
> Both options share the same core benefits, including better IDE/CLI
> auto-completion and quick data exploration, since they both start with
> FROM.
> The difference is:
>
> - Option A aligns with the approach used in DuckDB, helping maintain
> consistency with the existing implementation and making it more
> familiar to
> users migrating from other systems.
> - Option B aligns better with the actual execution logic and human
> thought process: first, you define the data source (FROM), then you
> filter
> it (WHERE), and finally, you choose what to project (SELECT)
>
> For more context, please refer to the discussion thread:
> https://lists.apache.org/thread/p1psfm5y9zo270tn75rz1cdglff7ogc8
>
> Please share your preference (Option A or Option B) and any additional
> thoughts.
>
> Best regards,
>
> Abdelrahman
>