-
Notifications
You must be signed in to change notification settings - Fork 636
feat(catalog): support DBeaver constraints view #15227
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, generation_expression
and is_generated
has been added in rw_columns
, you may need to resolve the conflict.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just restructured code to reduce indent.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Implemented
pg_catalog.pg_constraint
. Only primary keys are listed because this is the only constraints supported in RisingWave.closes #15197
closes #15205
Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
(No need to update any docs page)
pg_catalog.pg_constraint
for DBeaver compatibility.