From 5c4b46dc00fca8a519c2deb51c73d32d8d76fdae Mon Sep 17 00:00:00 2001 From: "marko.puric@canonical.com" Date: Tue, 25 Aug 2026 20:08:35 +0200 Subject: [PATCH] docs: note LightDB State array limitation Signed-off-by: Marko Puric --- .../application-services/1-lightdb-state/3-read-write-data.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/application-services/1-lightdb-state/3-read-write-data.md b/docs/application-services/1-lightdb-state/3-read-write-data.md index 4008cb83..7ac41c5a 100644 --- a/docs/application-services/1-lightdb-state/3-read-write-data.md +++ b/docs/application-services/1-lightdb-state/3-read-write-data.md @@ -20,6 +20,10 @@ We can start by saving temperature data on LightDB. On requests to write data, t - `integer` - `string` +:::note +Arrays are not supported. The API accepts them on write, but they are stored as objects with the element positions as keys, so `["a", "b"]` is saved as `{"0": "a", "1": "b"}`. +::: + import { ProtocolPublishSample, ProtocolReadSample, ProtocolDeleteSample } from '/docs/_partials-common/protocol.mdx' Here is a snippet of example code to save a temperature value of 30 Cº at path `/env/temp`