Postgresql migrations using rename column cause compilation error e.g ALTER TABLE X RENAME COLUMN y TO Z

[griffio]

SQLDelight Version

2.0.*

Operating System

Any

Gradle Version

Any

Kotlin Version

Any

Dialect

Postgresql

AGP Version

No response

Describe the Bug

When using migration files (sqm) the rename column causes compilation error - happens in 2.0.0 and 2.0.1

ALTER TABLE Address RENAME COLUMN address TO address_1;

Work-around - rename query files first as the problem appears to be the error annotations erroring with a class cast exception
either ColumnDefMixin or SqlColumnName

Stacktrace

Postgresql
Cause: class app.cash.sqldelight.dialects.postgresql.grammar.psi.impl.PostgreSqlAlterTableRenameColumnImpl cannot be cast to class com.alecstrong.sql.psi.core.psi.mixins.ColumnDefMixin (app.cash.sqldelight.dialects.postgresql.grammar.psi.impl.PostgreSqlAlterTableRenameColumnImpl and com.alecstrong.sql.psi.core.psi.mixins.ColumnDefMixin are in unnamed module of loader org.gradle.internal.classloader.VisitableURLClassLoader @22a8bdc3)

Gradle Build Script

postgresql

sqldelight {
    databases {
        create("Sample") {
            deriveSchemaFromMigrations.set(true)
            migrationOutputDirectory = file("$buildDir/generated/migrations")
            migrationOutputFileFormat = ".sql" // Defaults to .sql
            packageName.set("griffio.queries")
            dialect(libs.sqldelight.postgresql.dialect)
        }
    }
}

[griffio]

🚬 🤔 Sqlite has similar issues but needs it's own issue #4897 and PR as fixes are slightly different

[0xEDU]

Could you elaborate on the work around for this? I couldn't manage to make it work

[griffio]

🤔 @0xEDU - If I remember - this issue was one of several problems running migrations that I created PRs.
I believe that an error is thrown because as a result of changing - for example a column name with ALTER TABLE Address RENAME COLUMN address TO address_1; then naturally any queries won't compile that have the old name. However the class cast is thrown during that check. So - the work around was simply to ensure any queries using address are changed to address_1 before running the migration.
If you are running into problems - I have a project https://github.com/griffio/sqldelight-postgres-01 where I am tracking the migration fixes that I am making to save you from bashing your head 🤕