davis zhen
davis zhen
I get it. The problem will be delayed now. And It will be solved later 0.3 or earlier 0.4.
> First batch will support these format. DATE_FORMAT(b.measurement_time,'%Y-%m-%d') DATE_FORMAT(b.measurement_time,'%Y-%m') DATE_FORMAT(b.measurement_time,'%Y-%m-%d %H:%i:%s') > > As a p0 requirement, this function still needs to support more format in 0.6.0 We will implement...
Do not support date,datetime,timestamp in: Function 'variance' with parameters [DATE] will be implemented in future version. Function 'variance' with parameters [DATETIME] will be implemented in future version. Function 'variance' with...
@m-schen says that the implicit conversion will not happen in the aggregation function.
int64 -> decimal. problem: 1. decimal % decimal , no implementation in type analysis 2. cast error in execution ========== refresh error message. move to 0.6 .
????? -- @bvt:issue#3283 update t1 set a=a+101; select a,b from t1 order by 1; update t1 set a=27 where a=125; select a,b from t1 order by 1; update t1 set...
do not support,bool => float, decimal => bigint: Function 'sum' with parameters [BOOL] will be implemented in future version. Operator 'cast' with parameters [DECIMAL64 BIGINT] will be implemented in future...
@m-schen says that the implicit conversion will not happen in the aggregation function.
The function `bin` is wrong and contributed by an external author who have not fix it. So in migration plan, we decide to migrate it after it is fixed. Now,...
maybe move to 0.6