Alter table does not seem to work

[rstpv]

What happened?

Adding columns or dropping or renaming does fail / internal schema doesn't seem to pick the changes

What did you expect to happen?

As the table was modified through either adding a column, renaming a column or dropping a column I would expect those changes to be reflected

How can we reproduce it (as minimally and precisely as possible)?

            bigQuery.query(QueryJobConfiguration.of(
                "CREATE TABLE `$DATASET_NAME.customers` (name STRING)"
            ))
            bigQuery.query(
            QueryJobConfiguration.of(
                "ALTER TABLE `$DATASET_NAME.customers` ADD COLUMN age INTEGER"
            )
        )
        bigQuery.query(
            QueryJobConfiguration.of(
                "INSERT INTO `$DATASET_NAME.customers` (name, age) VALUES ('Alice', 30)"
            )
        )

Fails with

com.google.cloud.bigquery.BigQueryException: failed to analyze: Column age is not present in table test-project_test_12345_customers [at 1:72]

Anything else we need to know?

No response

[lraigosov]

A fix for this issue has been implemented in PR #492. The solution intercepts ALTER TABLE in both jobsInsertHandler and jobsQueryHandler, applying three coordinated updates within the active transaction: raw SQLite DDL via the inner connection, a UPSERT of the googlesqlite catalog, and a direct AddColumn call on the WASM-side SimpleTable so the column is visible to the ZetaSQL analyzer immediately. A regression test (TestDDLAlterTable) is included.

[lraigosov]

A fix is available in PR #495. The implementation intercepts ALTER TABLE in both query and insert handlers, applying three coordinated updates: raw SQLite DDL via the inner connection, UPSERT of the googlesqlite catalog, and a direct AddColumn call on the WASM-side SimpleTable so the ZetaSQL analyzer sees the new column immediately.