You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rather than use enums, we choose to use lookup tables.
Example:
CREATETABLE "status" (
id SMALLSERIAL NOT NULLPRIMARY KEY,
name TEXTNOT NULL UNIQUE
);
INSERT INTO"status" (id, name) VALUES (1, 'OPEN'), (2, 'CLOSED');
It would great if I could specify some tables that I would like the contents included in the diff and the created versioned migration file.
Something like: atlas migrate diff {{NAME}} --dir "file://{{PROJECT_PATH}}/migrations" --to "file://{{PROJECT_PATH}}/desired_end_state_schema.sql" --dev-url "docker://postgres/16.4/dev?search_path=public" --examine-content-tables "status,severity,etc"
The text was updated successfully, but these errors were encountered:
Rather than use enums, we choose to use lookup tables.
Example:
It would great if I could specify some tables that I would like the contents included in the diff and the created versioned migration file.
Something like:
atlas migrate diff {{NAME}} --dir "file://{{PROJECT_PATH}}/migrations" --to "file://{{PROJECT_PATH}}/desired_end_state_schema.sql" --dev-url "docker://postgres/16.4/dev?search_path=public" --examine-content-tables "status,severity,etc"
The text was updated successfully, but these errors were encountered: