iamlinjunhong
iamlinjunhong
Because parser is now a lexical analyzer corresponding to multiple dialects, there is a thread safety problem hard to solve gracefully when parsing different dialects concurrently. But mo just use...
Conversion rules are already defined. uint64, int64 will cast as int64, int64. You can use: SELECT * FROM numbers WHERE ui=cast(0 as unsigned);
> fix in pr #4483. It doesn't relate to the issue #3579
process: 1. refactor default value for create table 2. refactor default value for insert select 3. refactor insert values
Doesn't support cast decimal as bigint now. Discuss with @domingozhang that will put this issue to 0.6.
Has a conclusion that 0.5 doesn't support float/double with param of precision.
Discuss with @aressu1985, Cases will not modify and plan will not reject form of float/double with param. This issue can move into 0.6.
mysql does't support select cast(a as timestamp).
1. multiple table delete has done 2. multiple table update will finish on Jul 23, 2022 except update to default value 3. update to default value will finish after issue...
2 will finish on Jul 27, 2022, because interface of update that tae offers cancel.