docs(drivers): MQTT write QoS/claim backoff and Sql Postgres untyped binds (#602)

Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe
2026-10-08 07:32:42 -04:00
parent 275b240ebd
commit babc452740
2 changed files with 13 additions and 3 deletions
@@ -92,7 +92,10 @@ Both value-bearing fields — `whereValue` here and `keyValue` on the `KeyValue`
 authored as a JSON string, number or boolean, and are captured as text. They are **bound as
 parameters** either way, and matched back as text (the key cell is stringified), so a key column
 that holds an INTEGER station id can be authored either `"7"` or `7`. A JSON object, array or `null`
-is not a value and is refused. (They were read asymmetrically until 2026-08-10, so a numerically
+is not a value and is refused. On **PostgreSQL** a string bind is sent untyped (`NpgsqlDbType.Unknown`,
+`PostgresDialect.ConfigureParameter`, STAB-24) so the server infers its type from the compared column;
+bound as `text`, a `"7"` against an `integer` key fails with `operator does not exist: integer = text`.
+(They were read asymmetrically until 2026-08-10, so a numerically
 authored `keyValue` refused the tag while the identically-bound `whereValue` was served — and the
 deploy gate reported the key as *missing* when it was right there in the blob.)