[quinnj-bot]

json and jsonb columns decode to JSON.LazyValue. Binding one back as a parameter sent Julia's display of it (LazyObject{String} with 1 entry: ...). json and jsonb targets rejected that text (Token "LazyObject" is invalid), and text targets stored it silently. JSON.JSONText had the same problem.

Both now bind as their JSON text, as scalars and as array elements. The text comes from JSON.jl's public JSON.parse(x, JSONText), which returns the value's exact source text, so large numbers keep every digit.

j = only(DBInterface.execute(conn, """SELECT '{"a": 1}'::jsonb AS j""")).j
DBInterface.execute(conn, raw"INSERT INTO docs (body) VALUES ($1)", (j,))
# main: jsonb column -> error; text column -> stores "LazyObject{String} with 1 entry: ..."

This also matters for Postgres.load! in #37. On that branch, copying a query result that has a jsonb column creates a text column filled with "LazyObject{String}()". With this change applied on top of #37, the column holds the JSON text. The column type still comes from #37's type mapping.

Found by a differential check of Postgres.jl against psycopg 3 on PostgreSQL 16 (bound parameters of every type, read back through the binary protocol).

Verification

• New assertions next to the array type tests: they error on main and pass with this change.
• Write-path harness: lazy values, nested lazy values and JSONText, bound into json, jsonb and jsonb[], through unnamed execute, prepared execute, executemany and explicit casts. All are stored byte-for-byte as expected. WHERE v = $1 on jsonb matches the stored row.
• Full local Pkg.test() (Julia 1.12.6, Docker PostgreSQL 16): 9244/9244 passed.

🤖 Generated with Claude Code