Studio: Error when updating a jsonb[] column set with a default value as '[]'::jsonb

[monicakh]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Error when updating a jsonb[] column.

The error states "null value in column 'additional_items' of relation 'test' violates not-null constraint". This issue seems to be contradictory since a default value is set for the additional_items column as '[]'::jsonb, which should prevent it from being empty.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Create the following table definition:

create table public.test (
  id uuid not null default gen_random_uuid (),
  assignee text null,
  additional_items jsonb not null default '[]'::jsonb,
  constraint test_pkey primary key (id)
);

2. Insert data into the table but omit additional_items column
3. Attempt to update a row by providing a value for the additional_items column
4. Instead of updating the row successfully, the error message "Failed to run sql query: null value in column "additional_items" of relation "test" violates not-null constraint" is thrown, indicating that the additional_items column is treated as null despite the default value being set.

Expected behavior

The update operation should succeed without any errors, as the additional_items column has a default value of '[]'::jsonb, ensuring that it is never empty.

Screenshots

System information

• OS: macOS
• Browser Chrome

Additional context

The error occurs only during updates; inserting data into the table works as expected.
The issue persists even when explicitly providing a non-null value during the update operation.