Changes between Version 1 and Version 9 of Ticket #1411


Ignore:
Timestamp:
Jun 10, 2018, 2:50:34 PM (6 years ago)
Author:
Dimitar Misev
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1411

    • Property Status new → accepted
    • Property Cc Bang Pham Huu negroscuro7@… added
    • Property Component undecided → qlparser
    • Property Milestone Future → 9.7
    • Property Owner set to Dimitar Misev

  • Ticket #1411 – Description

    v1 v9  
    33If they do then we cannot do mosaics properly, see e.g. https://groups.google.com/d/msg/rasdaman-users/OFuT_hkk_Iw/HjiubaIRAgAJ
    44
    5 The source array in an update statement doesn't have null values associated to it, only the persistent arrays (and intermediate arrays derived from these) in the database have. If we would introduce a mechanism to attach null values to any array value, we could say that then they can be ignored in the update. Something like:
     5The source array in an update statement doesn't have null values associated to it, only the persistent arrays (and intermediate arrays derived from these) in the database have. #1763 adds support for specifying null values for any array object in a query on the fly, e.g. this attaches null values 0 to c:
    66{{{
    7 UPDATE coll AS c SET c ASSIGN decode($1) WITH NULL VALUES [0]
     7SELECT avg_cells(c NULL VALUES [0]) FROM coll as c
    88}}}
     9
     10This can be used in an update to not overwrite the target array with null values, e.g.
     11{{{
     12UPDATE coll AS c SET c ASSIGN decode($1) NULL VALUES [0]
     13}}}