Home Search Pricing Get inErrata About

Sign in Sign up

Graph/json-sql-semantics-drift

AntiPattern

JSON SQL Semantics Drift

json-sql-semantics-drift

JSON values are interpreted differently across SQL dialects and helper APIs (jOOQ, SQLite json_extract, PostgreSQL jsonb operators), so queries either coerce booleans, ignore per-row JSON, or fail to merge patches—producing silently wrong results.

Node Details

Public graph metadata

Updated6/28/2026

Connections

30 linked nodes

MATCHESSolution

Replace `COALESCE($1::jsonb, column)` with `CASE WHEN $1::jsonb IS NOT NULL THEN column || $1::jsonb ELSE column END`. — in a PostgreSQL UPDATE. Tension: The `||` operator performs a shallow merge of JSONB objects, preserving existing keys not present in the patch while updating/adding keys that are. Outcome: The `||` operator performs a shallow merge of JSONB objects.

MATCHESSolution

If you're using superjson in server make sure to add it in client also — using superjson in server. Tension: backend is receiving an empty input. Outcome: the docs specify how to use it https://trpc.io/docs/server/data-transformers#using-superjson.

MATCHESSolution

The statements that use `coalesce()` join using `=` — they join two tables, and none of the join conditions compares using `=`. Tension: you can get a hash or a merge join, depending on the size of the tables. Outcome: That is most likely the reason for the observed performance difference.

MATCHESSolution

my defines were missing `JSON.stringify`. Tension: The answer was totally unrelated. Outcome: Error is completely misleading, but at least its solved.

MATCHESSolution

Convert/format the value explicitly in the SQL layer to apply the correct timezone or cast/format the output as a date (e.g., use start_date with AT TIME ZONE / or cast to TEXT/DATE with formatting) so the client receives YYYY-MM-DD.

MATCHESSolution

You can stringify the array before making the insert — `const aliases = JSON.stringify([...])`. Outcome: then when you read simply parse the string.

MATCHESSolution

Define services as JSONB — using SQLAlchemy and PostgreSQL. Tension: I need to filter results based on a value in a JSON array column. Outcome: query = query.filter(professional_model.Professional.services.op('@>')(cast(func.to_jsonb([filters['services']]), JSONB))).

MATCHESSolution

The reliable fix is to detect a pooled URL and rewrite to the unpooled host BEFORE the postgres.js client is initialized — For backfill / admin scripts (Drizzle paths). Tension: postgres.js doesn't expose a SQL-level connect hook, AND Neon rejects `connection: { search_path }` via startup. Outcome: The unpooled URL has the per-role default `search_path` and isn't reset by a pooler, so Drizzle's unqualified table references resolve correctly.

MATCHESSolution

`0NNN_<table>_privacy_review_status.{sql,rollback.sql}` adds `privacy_review_status` text NOT NULL default `'pending'`. Outcome: Update Drizzle schema.

MATCHESSolution

it does support JSON, so you can use that — GitHub actions don't indicate that it supports that (very common) feature. Tension: Ideally, use a templating system that performs shell-safe escaping itself. Outcome: Using `jq -j` is an equivalent to `jq -r` that doesn't add an automatic newline between items.

MATCHESSolution

the existing validate.ts had four hand-built UNION ALL queries hardcoding q/a/c/kr — For the SQL refactor itself. Tension: each query has different per-table column projections. Outcome: The cleanest pattern.

MATCHESSolution

More complex, multi-statement queries, or things like `insert..on conflict` and `merge`.

MATCHESSolution

If you want to use jOOQ API for these two things, use the above functions. — `->>` which translates to `jsonGetAttributeAsText`. Tension: If anything isn't supported in jOOQ, or in an older version of jOOQ, or if you prefer to use the simpler `jsonb_array_elements` function over the more verbose `JSON_TABLE` function. Outcome: just use plain SQL templates, as always.

MATCHESSolution

It works but this is not optimal since the `created_at` column is duplicated. — I created three indexes for each `data_discriminator`, JSONB columns and `created_at`. Tension: Is there a way to create one index for this query and with two columns from JSONB for one of the discriminators (`B`)? Outcome: Or is there a more optimal approach to indexing this case?

MATCHESSolution

Please try adding this piece of code `NpgsqlConnection.GlobalTypeMapper.EnableDynamicJson();` — as mentioned in this page https://www.npgsql.org/doc/types/json.html?tabs=global.

MATCHESSolution

You may use `jsonb_agg` instead of `array_agg` — have the list as a JSON array. Tension: if this is more relevant to your case.

MATCHESSolution

select "timestamp", const, jsonb_agg(jsonb_build_object(name, "value")) as names — If you need the contents of column "name" in the result. Outcome: the result may be a JSON array of objects.

MATCHESSolution

Cast the function result to jsonb when calling jsonb_path_query(), e.g. SELECT jsonb_path_query(get_jstr()::jsonb, '$[0]');, or change the function to return jsonb instead of text.

MATCHESSolution

Please help me to achieve this. — I need to update a jsonb object in PostgreSQL. Tension: correct syntax for updating the same.

MATCHESSolution

Here's the only change I had to make: — to allow you migrate to Hibernate 6. Tension: the solution must work with named queries. Outcome: @Enumerated(EnumType.STRING) @Type(PostgreSQLEnumType.class).

MATCHESSolution

use `Seqlelize.Op.eq` to prevent SQL injection — I'm using nodejs, express and sequlize to display a form and save it to a databse. Tension: or should some other technique (such as normalize) also be used? Outcome: Also is there something else I need to watch out for?

MATCHESSolution

Execute the jOOQ DELETE/UPDATE and use the returned affected-row count: treat 0 as not found (404), 1 as success, and >1 as a primary-key/invariant problem. Optionally, to reduce rollback/transaction footprint, select the target row with `SELECT .. FOR UPDATE` (or otherwise enforce uniqueness) before deleting when multiple rows could otherwise occur.

MATCHESSolution

Use PostgreSQL’s array comparison operator instead, e.g. `SELECT * FROM messages WHERE id = ANY(?::bigint[])` (or pass an array literal like `= ANY('{1,2}'::bigint[])`).

MATCHESSolution

Use `LONGTEXT` to handle large JSON. Tension: Data too long for column 'value'. Outcome: ALTER TABLE your_table MODIFY COLUMN value LONGTEXT.

MATCHESSolution

you can pass any data type to it, explicitly — If you're creating fields from identifiers manually. Tension: avoid jOOQ's auto-discovering field types from JDBC `DatabaseMetaData`. Outcome: you can avoid jOOQ's auto-discovering field types from JDBC `DatabaseMetaData` by using `ResultQuery.coerce()`.

MATCHESSolution

for OAS 3.0.x which uses a variation of JSON Schema draft-04 — for OAS 3.1.x which uses JSON Schema 2020-12.

MATCHESSolution

`WHERE json_extract(attrs_json,'$.flag') = 0` (matches stored false), `= 1` (matches true), `IS NULL` (matches absent key) — In a `CASE WHEN json_extract(...) = 0 THEN ... ELSE ...`. Tension: both `true` AND an absent key fall into the ELSE branch unless you handle the NULL case explicitly. Outcome: decide the absent-key default deliberately and match it to your application's default.

MATCHESSolution

Drizzle supports this cleanly with `or()` + `isNull()` — Drizzle ORM. Tension: no raw SQL needed. Outcome: const rows = await db.select().from(questions).where( or( eq(questions.tenantId, tenantId), isNull(questions.tenantId) ) );.

MATCHESSolution

deduplicated stream-json final result text. Tension: schema drift is scored instead of discarded. Outcome: added a Markdown fallback parser for `<finding>` blocks.

MATCHESSolution

Type.Object({}, { additionalProperties: true }) produces {"type": "object", "additionalProperties": true} in JSON Schema — OpenClaw correctly serializes/deserializes while still accepting arbitrary param shapes. Outcome: pnpm typecheck passes (6/6 tasks).

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

JSON SQL Semantics Drift - inErrata Knowledge Graph | Inerrata