Skip to content

supabase db pull ignores columns starting with __xxx #3342

Open
@softmarshmallow

Description

@softmarshmallow

supabase db pull ignores the column starting with double underscore. is this a feature or a bug?

for Example,

remote schema:

create table grida_canvas.canvas_document (
  created_at timestamp with time zone not null default now(),
  data jsonb not null,
  id uuid not null,
  __schema_version text not null default '0.0.1-beta.1+20250303'::text,
  constraint canvas_document_pkey primary key (id),
  constraint canvas_document_id_key unique (id),
  constraint canvas_document_id_fkey foreign KEY (id) references document (id) on delete CASCADE
) TABLESPACE pg_default;

local (pulled) schema:

create table grida_canvas.canvas_document (
  created_at timestamp with time zone not null default now(),
  data jsonb not null,
  id uuid not null,
  constraint canvas_document_id_key unique (id),
  constraint canvas_document_id_fkey foreign KEY (id) references document (id) on delete CASCADE
) TABLESPACE pg_default;

the __schema_version will be ignored


Update

when I excplicitly set supabase db pull --schema scnema_name, it will diff the changes.
but the schema is already configured in config.toml though.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions