Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sql: handle RENAME COLUMN on REGIONAL BY ROW crdb_internal_region column #59116

Closed
otan opened this issue Jan 18, 2021 · 1 comment · Fixed by #60638
Closed

sql: handle RENAME COLUMN on REGIONAL BY ROW crdb_internal_region column #59116

otan opened this issue Jan 18, 2021 · 1 comment · Fixed by #60638
Assignees
Labels
A-multiregion Related to multi-region C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Comments

@otan
Copy link
Contributor

otan commented Jan 18, 2021

Potentially block for implicit crdb_region.

For REGIONAL BY ROW AS ..., change the table descriptor.

@blathers-crl
Copy link

blathers-crl bot commented Jan 18, 2021

Hi @otan, please add a C-ategory label to your issue. Check out the label system docs.

While you're here, please consider adding an A- label to help keep our repository tidy.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.

@otan otan added A-multiregion Related to multi-region C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) labels Jan 18, 2021
@otan otan changed the title sql: handle RENAME COLUMN on regional by row sql: handle RENAME COLUMN on REGIONAL BY ROW crdb_internal_region column Feb 1, 2021
@otan otan self-assigned this Feb 16, 2021
@craig craig bot closed this as completed in 1a43d11 Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-multiregion Related to multi-region C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant