2 Commits

Include renames

Author	SHA1	Message	Date
Hein	a74eebc7f3	fix(json-columns): skip JSON select columns with no model scan target ... Requesting a JSON sub-field (e.g. jsonvalue->'product'->>'cost') that has no matching bun scanonly field on the model made the whole read fail with "bun: ModelX does not have column Y", since bun scans SELECT results straight into the typed model struct. Add reflection.HasColumn to check whether the model can actually receive a given column (including scanonly fields, walking embedded structs), and gate the JSON select-column expression on it in ApplySelectColumns (shared by websocketspec/mqttspec) and the resolvespec/restheadspec handlers. When there's no scan target, drop just that column with a warning instead of erroring the whole request.	2026-09-28 12:30:56 +02:00
Hein	206edd4bfd	feat: add JSON/JSONB sub-field select, filter and sort ... Support column references that traverse into JSON/JSONB values — data->>'x', data#>>'{a,b}', data->'a'->>'b', and the dotted data.a.b shorthand — in SELECT column lists, WHERE filters and ORDER BY, across the restheadspec, resolvespec, websocketspec and mqttspec handlers. - pkg/common/json_column.go: canonical ParseColumnRef + ColumnRef.SQL() builder. JSON path segments are bound as a single ?::text[] parameter, never interpolated; cast targets are whitelisted via NormalizeCastTarget. - pkg/common/json_condition.go: shared entry points mirroring BuildSpatialCondition - ResolveJSONColumnExpr (select/sort), BuildJSONFilterCondition (where, full operator set; infers ::numeric for ordered comparisons on numeric values when no explicit cast is given), and the ApplySelectColumns helper. - pkg/reflection.IsJSONColumn / pkg/spectypes.IsJSONType: disambiguate the dotted shorthand (data.city is JSON only when the base is a JSON column). - pkg/common/validation.go: ColumnValidator accepts JSON tokens. - Handlers: thread model through the filter call chains and wire the select/sort paths. funcspec (raw-SQL string builder, no param binding or model) and the FetchRowNumber raw-SQL builders are left as follow-ups, as is OpenAPI reporting of JSON sub-field columns.	2026-09-07 17:05:52 +02:00