-
Notifications
You must be signed in to change notification settings - Fork 595
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
support column comments #12663
Comments
I have a concern that probably many users will use tools like DBeaver to read/write comments, so we'd better maintain PG compatibility for this feature. |
Do you mean that DBeaver may be unable to recognize RisingWave's custom sytnax? This is a valid point. To be specific, my idea is that:
|
Just adding some links: The PostgreSQL doc suggests comments are not limited to columns, and they are stored separately then joined, rather than as an attribute of column. |
That's right. I guess that's why COMMENT ON comes into play. Commenting on CREATE TABLE is rather limited bcs only columns can have comments. |
Is your feature request related to a problem? Please describe.
There are many databases that allows commenting on columns, either during CREATE TABLE or after table creation through commands like COMMENT ON.
During CREATE TABLE
COMMENT ON
Apparently, column comment has been widely supported by many popular SQL systems. COMMENT ON is in favor of by primarily the PG and Oracle families while big data and MySQL families prefer the other. Snowflake supports the both.
I personally prefer Snowflake's syntax that combines both conventions:
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: