We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
__xxx
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
__schema_version
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.
supabase db pull --schema scnema_name
The text was updated successfully, but these errors were encountered:
No branches or pull requests
supabase db pull ignores the column starting with double underscore. is this a feature or a bug?
for Example,
remote schema:
local (pulled) schema:
the
__schema_version
will be ignoredUpdate
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.
The text was updated successfully, but these errors were encountered: