[Tarantool-discussions] Implicit cast for COMPARISON
Mergen Imeev
imeevma at tarantool.org
Tue Jan 21 14:11:08 MSK 2020
Hi all,
I would like once again ask a question about implicit cast for
COMPARISON. Currently the chart of implicit cast for COMPARISON
looks this way:
To BOOL | To INT | To DBL | To STR | To BIN
---------------------------------------------------------
>From BOOL | A | - | - | - | -
>From INT | - | A | A | A | -
>From DBL | - | A | A | A | -
>From STR | - | S | S | A | -
>From BIN | - | - | - | - | A
I suggested to change this chart so that is should look this way:
To BOOL | To NUM | To STR | To BIN
-----------------------------------------------
>From BOOL | A | - | - | -
>From NUM | - | A | - | -
>From STR | - | - | A | -
>From BIN | - | - | - | A
At the moment the only thing that different in these charts is
impicit cast from STRING to number and from number to STRING.
I asked the Russian community in Telegram about whether to allow
this implicit cast for COMPARISON. At the moment, 31 people have
voted, and 25 of them have voted for dropping this implicit cast.
So, once again I suggest using these rules:
1) The values of numeric types are comparable without any implicit
cast.
2) If the type of one of the values contains the type of another
value, then they are comparable.
3) In any other cases, the values are not comparable.
About "one type contains another type": we can say that INTEGER
contains UNSIGNED; NUMBER contains INTEGER, UNSIGNED, DOUBLE;
SCALAR contains all available in SQL types.
Since all numeric types are comparable, my suggestion means that a
value of any type can be compared with a value of type SCALAR. And
in this comparison, the same rules will be used as in no-SQL
Tarantool. For example, any value of type STRING is greater than
any value of type INTEGER.
What do you think about this?
More information about the Tarantool-discussions
mailing list