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.
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.