Why does atlas migrate diff fail with the following error after running atlas migrate apply?
Error: sql/migrate: connected database is not clean: found table "atlas_schema_revisions" in schema <schema_name>. baseline version or allow-dirty is required
How to generate an SQL schema file from an existing migrations directory to quickly set up a database for integration tests?
How do I fix the ModifySchema is not allowed when migration plan is scoped to one schema error?
How do I resolve MySQL Error 1049: Unknown database when connecting using a URL like: mysql://user:pass@host:port/<database_name>?
Error: mysql: query system variables: Error 1049 (42000): Unknown database '<database_name>'
What does this error mean, and how can I fix it?
How can I define functional indexes in MySQL using Atlas HCL syntax?
How do I configure Atlas to load the database schema from nested directories with HCL files?
/project
├── main.sql
├── extensions
└── schemas
└── public
├── public.sql
├── tables
│ ├── pets.sql
│ ├── posts.sql
│ ├── profiles.sql
│ └── user_groups.sql
├── functions/
└── types/
After upgrading Atlas, you might encounter an error stating "Feature X is no longer supported by this release."
For example:
Error: data.external_schema is no longer supported by this release.
This occurs when you install the community version of Atlas, which lacks some features available only in non-community builds.
To include a PostgreSQL extension in your schema, there are a few configurations to be made to ensure the extension is properly applied.
How to test PostgreSQL Row-Level Security (RLS) policies using Atlas.
Applications often rely on a static dataset to pre-exist in the database in order to function. Examples for such datasets include user roles, country names, or product categories.
The process of populating the database with this initial data is called "seeding". This guide will show you how to seed your database using Atlas.