Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

supabase db pull ignores columns starting with __xxx #3342

Open
softmarshmallow opened this issue Mar 23, 2025 · 0 comments
Open

supabase db pull ignores columns starting with __xxx #3342

softmarshmallow opened this issue Mar 23, 2025 · 0 comments

Comments

@softmarshmallow
Copy link

softmarshmallow commented Mar 23, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant