-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: implement ALTER TABLE ... ALTER COLUMN SET [VISIBLE|NOT VISIBLE] #62892
Comments
Hi, I'm new to cockroachdb, but I'm willing to give it a try, can I work on it? |
63052: sql: support alter column SET VISIBLE and NOT VISIBLE to unhide or hide column r=otan a=kurokochin Addresses #62892 Co-authored-by: kurokochin <[email protected]>
just checking: does #63052 close this? |
I think we're back porting this to 21.1.1 |
Yeah, that's right - 21.1.1.
Is there some place where we're keeping track of the deferred backports?
…On Wed, Apr 14, 2021 at 8:58 PM Oliver Tan ***@***.***> wrote:
I think we're back porting this to 21.1.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#62892 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMXVOT7HK627ZCNAICFCADTIY24TANCNFSM42FLILFA>
.
|
@ajstorm The convention is to use the However, that's not super easy to track, (as I posited in Slack https://cockroachlabs.slack.com/archives/C0HM2DZ34/p1618516063393000) so I'm going to try to make https://backboard.crdb.dev/ understand these labels in some way |
This just needs backporting now. |
This was fixed by #63052. Closing. |
In #58923, we added the ability to set a column as VISIBLE and NOT VISIBLE.
We now need the ability to have
ALTER COLUMN <col> SET [VISIBLE|NOT VISIBLE]
.The changes to do this are as follows (you can follow SET DEFAULT as a guideline for what to write)
type AlterTableSetVisible struct { Visible bool }
struct to tree/alter_table.go, similar toAlterTableSetDefault
.Hidden
inalter_table.go
logic_test/alter_table
Allow for ALTER COLUMN <column_name> SET NOT VISIBLE. When implemented, this statement will allow users to make their columns invisible. This functionality is required if customers want to build their own REGIONAL BY ROW tables (using REGIONAL BY ROW AS) and have them look identically to how they'd be created by the system.
The text was updated successfully, but these errors were encountered: