Informix - Problem description
Problem IT07901 | Status: Closed |
BSON_UPDATE() $SET OPERATOR NOT BEHAVING AS IT SHOULD | |
product: | |
INFORMIX SERVER / 5725A3900 / B70 - IDS 11.70 | |
Problem description: | |
bson_update(<bson>, "{$set:<update_json_string>}") working in most simplistic cases only: - <update_json_string> can only contain a single key - that key needs to exist already in <bson> - its existing value, if complex, must have exactly same structure as new one For instance you would have this bson: {a : 1, b : 2} You can say {$set : {a : 10}} or {$set : {b : 20}} but {$set : {a : 10, b : 20}} would run into 9659: The server does not support the specified UPDATE operation on JSON documents. Same for {$set : {c : 30}} where key 'c' had not existed before. You also could say {$set : {b : { b1 : 11, b2 : 12}}}, so replace key b's value by a more complex one, but then only e.g. {$set : {b : { b1 : 21, b2 : 22}}} would work on this, and not e.g. {$set : {b : { b1 : 21, b2 : 22, b3 : 33}}} or {$set : {b : 22}} These quite confusingly now would run into -201 SQL syntax error - during execution of the command. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All NoSQL users using bson_update($set) * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 12.10.xC6 * **************************************************************** | |
Local Fix: | |
Solution | |
Problem Fixed In IBM Informix Server 12.10.xC6 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.03.2015 30.12.2015 30.12.2015 |
Problem solved at the following versions (IBM BugInfos) | |
12.10.xC6 | |
Problem solved according to the fixlist(s) of the following version(s) | |
12.10.xC5.W1 | |
12.10.xC6 |