[Tarantool-patches] [PATCH v1 7/7] sql: fix comparison with SCALAR value

[Mergen Imeev]

On Thu, Aug 12, 2021 at 09:50:35PM +0300, Vladislav Shpilevoy wrote:
> Thanks for the patch!
> 
> On 11.08.2021 19:01, Mergen Imeev via Tarantool-patches wrote:
> > After this patch, SCALAR values will be able to be compared with values
> > of any other scalar type. The comparison will be done according to the
> > SCALAR rules, which means boolean values < numeric values < string
> > values < binary values < uuid values.
> > 
> > Closes #6221
> 
> Could you please add a docbot request?

Fixed:


commit 6179b16e422a1349ebe5b0ed340c81d8f5a4e6a2
Author: Mergen Imeev <imeevma at gmail.com>
Date:   Wed Aug 11 14:58:23 2021 +0300

    sql: fix comparison with SCALAR value
    
    After this patch, SCALAR values will be able to be compared with values
    of any other scalar type. The comparison will be done according to the
    SCALAR rules, which means boolean values < numeric values < string
    values < binary values < uuid values.
    
    Closes #6221
    
    @TarantoolBot document
    Title: SCALAR and NUMBER values in SQL
    
    SCALAR values can now be compared with values of any other scalar type,
    but cannot be implicitly cast to any other scalar type. This means that
    SCALAR values cannot participate in arithmetic, bitwise operations,
    concatenation, or functions that, by definition, do not accept SCALAR
    values.
    
    NUMBER values now also cannot be implicitly cast to any other numeric
    type, which means that NUMBER values cannot participate in arithmetic
    and bitwise operations, or in functions that, by definition, do not
    accept NUMBER values.