Missing Schema Prefix in DDL RENAME Statement

[mpyw]

Description

When using the Atlas HCL migration tool to rename an index from "a" to "b", the generated DDL statement for the RENAME operation lacks the schema name prefix. This causes a pq: relation not found error when working with schemas other than public in PostgreSQL.

Steps to Reproduce

1. Create a schema other than public in PostgreSQL (e.g., custom_schema).
2. Use Atlas HCL to define an index a in this custom schema.
3. Use Atlas HCL to rename the index a to b.
4. Observe the generated DDL statement for the RENAME operation.

Expected Behavior

The generated DDL statement should include the schema name prefix for the index being renamed. For example:

ALTER INDEX "custom_schema"."a" RENAME TO "b";

Actual Behavior

The generated DDL statement lacks the schema name prefix, resulting in an error:

ALTER INDEX "a" RENAME TO "b";

Error: pq: relation "a" not found

Environment

• Atlas HCL Version: v0.24.1-6857ea8-canary
• PostgreSQL Version: public.ecr.aws/docker/library/postgres:15.4

Additional Context

This issue appears when working with schemas other than public in PostgreSQL. The lack of a schema name prefix in the RENAME statement causes PostgreSQL to search for the index in the public schema, leading to a relation not found error if the index is in a different schema.

[a8m]

Hey @mpyw, what URL did you use? See: https://atlasgo.io/concepts/url#scope

Also, please upgrade to latest Atlas and check this.

[a8m]

From docs:

When the database URL is set to a specific schema (e.g., postgres://postgres:pass@host:port/db?search_path=public&sslmode=disable), the scope of the work done by Atlas (inspection, diffing, planning, applying, etc.) is limited to one schema. As a result, DDL statements printed during diffing or planning will be formatted without schema qualifiers and can be executed on any schema. e.g., table instead of schema.table

However, if the database URL does not specify a schema (i.e., without the search_path), Atlas operates on the selected schemas (defaulting to all), and the generated DDL statements include schema qualifiers. e.g., schema.table instead of table.

Closing, but feel free to reopen if you still need help with this.

[mpyw]

@a8m The database URL is postgresql://<USER>:<PW>@localhost:5432/<DBNAME>?sslmode=disable. And the most of other statements (execpt RENAME) qualify with the schema prefix. I believe this is the bug.

[mpyw]

I'll reopen as a new issue.