Skip to content

Conversation

@fulghum
Copy link
Contributor

@fulghum fulghum commented Mar 17, 2025

When building plan nodes to handle altering a column's nullability or type, without respecifying the full column definition, the built node should ensure any column default expressions are resolved.

This originally showed up as a panic in Doltgres, because Doltgres' TypeSanitzer found the UnresolvedColumnDefault instance and tried to invoke operations on it.

Note that it's not currently possible to trigger this issue with Dolt or GMS because MySQL has a more limited syntax than Postgres for altering a column without respecfiying its full column definition, and Dolt/GMS does not support that syntax currently (e.g. ALTER TABLE t ALTER COLUMN SET VISIBLE).

Copy link
Member

@zachmu zachmu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fulghum fulghum force-pushed the fulghum/alter_column branch from 0ae3dac to 57bf63c Compare March 17, 2025 23:16
@fulghum fulghum merged commit fa97159 into main Mar 17, 2025
8 checks passed
@fulghum fulghum deleted the fulghum/alter_column branch March 17, 2025 23:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants