Changes between Version 1 and Version 2 of Ticket #2754


Ignore:
Timestamp:
Jul 31, 2023, 10:48:18 AM (15 months ago)
Author:
Dimitar Misev
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2754 – Description

    v1 v2  
    22r="rasql --user rasadmin --passwd rasadmin"
    33$r -q 'create collection test_sdom_error GreySet3'
    4 $r -q 'insert into test_sdom_error values marray i in [0:0,0:0,0:0] values 200c'
     4$r -q 'insert into test_sdom_error values marray i in [0:0,0:0,0:0] values 0c'
    55$r -q 'update test_sdom_error as c set c assign marray i in [2:2,2035:3034,126:1125] values 200c'
    66$r -q 'update test_sdom_error as c set c assign marray i in [2:2,2035:3034,1126:1375] values 200c'
    77$r -q 'update test_sdom_error as c set c assign marray i in [2:2,3035:3051,126:1125] values 200c'
    88$r -q 'update test_sdom_error as c set c assign marray i in [2:2,3035:3051,1126:1375] values 200c'
     9$r -q 'update test_sdom_error as c set c assign marray i in [1:1,3199:3204,-9:1302] values 100c'
    910
    10 $r -q 'SELECT
    11         scale(
    12           c0[2,2446:3204,-9:1166],
    13           [0:257, 0:337]
    14         )[172:257, 47:191]
    15   FROM test_sdom_error AS c0'
     11$r -q 'c0[2,2446:3204,-9:1166] FROM test_sdom_error AS c0'
    1612}}}
    1713the SELECT query throws
    … …  
    2117but it should work without error.
    2218
     19The problem I guess is that the slice at `[2,...]` has sdom `[2:2,2035:3051,126:1375]` which doesn't cover `[2,2446:3204,-9:1166]`.
     20
     21However, the full sdom of the array is `[0:2,0:3204,-9:1375]`, which covers fine that subset, so no error should be thrown.