This is QVariant, specifically how variants in QML behave, and not deliberate on U1Db's part.
The only way to address this would be to re-consider the API or try to replace QVariant. ** Package changed: ubuntu-ui-toolkit (Ubuntu) => u1db-qt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to u1db-qt in Ubuntu. https://bugs.launchpad.net/bugs/1465003 Title: U1db.Document silently ignores key assignment Status in u1db-qt package in Ubuntu: Confirmed Bug description: "document.contents[foo] = bar" has no effect. This results in needing to write the above code as: var temp = document.contents temp[foo] = bar document.contents = temp This is annoying and ugly code everytime I want to update a single value. Proposed solution: Allow saving keys directly. If for some reason this is absolutely not possible, atleast throw an error or display a warning when an assignment is attempted, as it is clearly not the desired behaviour that the above line of code does absolutely nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u1db-qt/+bug/1465003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp

