Opened 8 years ago
Last modified 6 years ago
#1411 closed question
Updates should ignore null values? — at Version 1
| Reported by: | Dimitar Misev | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 9.7 |
| Component: | qlparser | Version: | development |
| Keywords: | Cc: | Peter Baumann, Vlad Merticariu, Bang Pham Huu, negroscuro7@… | |
| Complexity: | Medium |
Description (last modified by )
In an update, if the source array contains null values, should they overwrite the existing values in the target array?
If they do then we cannot do mosaics properly, see e.g. https://groups.google.com/d/msg/rasdaman-users/OFuT_hkk_Iw/HjiubaIRAgAJ
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:
UPDATE coll AS c SET c ASSIGN decode($1) WITH NULL VALUES [0]
Note:
See TracTickets
for help on using tickets.
