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
When attempting to run a set of migrations against an existing database, I get the following error: Error: sql/schema: modify "atlas_schema_revisions" table: pq: at or near "access": syntax error
It fails when there is an existing atlas_schema_revision table only. If I delete the table and re-run, it will regenerate it, though the schema it creates is the same as the old one. Running the update again against the newly created version also fails.
This command worked in version 0.26 of the CLI.
Here's the command that I'm using: atlas migrate apply --url "postgres://$FW_CRDB_USER:$FW_CRDB_PASSWORD@$FW_CRDB_HOST:$FW_CRDB_PORT/exchange_sitemanager" --dir file://ent/migrate/migrations --allow-dirty --revisions-schema public --dry-run
using:
atlas version
atlas version v0.30.1-614b10f-canary
https://github.com/ariga/atlas/releases/latest
on MacOS, though the same error occurs when deployed via docker/kube
My database logs don't show me anything useful at this point so I'm a little stuck on how to troubleshoot.
The text was updated successfully, but these errors were encountered:
When attempting to run a set of migrations against an existing database, I get the following error:
Error: sql/schema: modify "atlas_schema_revisions" table: pq: at or near "access": syntax error
It fails when there is an existing
atlas_schema_revision
table only. If I delete the table and re-run, it will regenerate it, though the schema it creates is the same as the old one. Running the update again against the newly created version also fails.This command worked in version 0.26 of the CLI.
Here's the command that I'm using:
atlas migrate apply --url "postgres://$FW_CRDB_USER:$FW_CRDB_PASSWORD@$FW_CRDB_HOST:$FW_CRDB_PORT/exchange_sitemanager" --dir file://ent/migrate/migrations --allow-dirty --revisions-schema public --dry-run
using:
on MacOS, though the same error occurs when deployed via docker/kube
My database logs don't show me anything useful at this point so I'm a little stuck on how to troubleshoot.
The text was updated successfully, but these errors were encountered: