From 9f0ae455378d5ce16dc833bdbea9a4b86607364a Mon Sep 17 00:00:00 2001 From: harsh mahajan Date: Fri, 7 Aug 2026 10:49:32 +0530 Subject: [PATCH] fix(databases): render array column items with their element type The string fallback in the row column renderer exists for the spreadsheet inline cell editor, where an entire array is edited as one comma-separated textarea. It keyed off `column.array` (the column definition) rather than the `array` prop (the render mode). In the full row create/edit form, columnItem renders one Column per array element and deliberately omits the `array` prop so each item gets its element-type input. Since `column.array` was still true, every item collapsed to a string input -- a Boolean[] column showed "Enter string". This also caused intermittent save failures: the string component still ran parseValue() against column.type, so literal true/false/1/0 coerced and saved, while anything else yielded null, and a null inside a typed array is rejected by the API. Keying off the `array` prop restores per-item typed inputs (boolean select, number input with min/max, date picker) while leaving the spreadsheet cell editor and its "Advanced edit" link untouched, since only the two fromSpreadsheet branches pass `array`. --- .../table-[table]/rows/columns/column.svelte | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/column.svelte b/src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/column.svelte index 37947fefe..1f385d75a 100644 --- a/src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/column.svelte +++ b/src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/rows/columns/column.svelte @@ -88,7 +88,7 @@ {:else}