t; >
> >
> >
> >
> >
> >
> > --原始邮件--
> > 发件人:"Xiangdong Huang" > 发送时间:2020年2月7日(星期五) 下午2:58
> > 收件人:"dev" >
> > 主题:Re: [DISCUSS] Table schema of group by device
> >
>
-原始邮件--
> 发件人:"Xiangdong Huang" 发送时间:2020年2月7日(星期五) 下午2:58
> 收件人:"dev"
> 主题:Re: [DISCUSS] Table schema of group by device
>
>
>
> One more suggestion, using "align by device" is more clear than "group by
>
One more suggestion, using "align by device" is more clear than "group by
device".
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Xiangdong Huang 于2020年2月7日周五 下午2:56写道：
> -1 for (2), forever and I think I will never vote +1 for
-1 for (2), forever and I think I will never vote +1 for it...
If you do it like that, there is no chance to replace those applications
which are using relational db to manage timeseries data.
(3) is the most friendly for those developers who are using Relational DB,
because when they write a
Hi,
In IOTDB-243 [1], We want to allow create measurements with the same name
but with different types in the same storage group.
For example,
root.sg1.d1.s1, int32
root.sg1.d1.s2 int32
root.sg1.d2.s1 boolean
root.sg1.d2.s2 int32
This may cause trouble in group by device query. How do we
