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.

Sign up for GitHub

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

Jump to bottom

bug: Mismatch in PG and RW frontend output for DDL statements, should have whitespace rather than underscore delimiters #16557

Open
kwannoel opened this issue Apr 30, 2024 · 2 comments
Open

bug: Mismatch in PG and RW frontend output for DDL statements, should have whitespace rather than underscore delimiters #16557

kwannoel opened this issue Apr 30, 2024 · 2 comments
Labels
no-issue-activity priority/low type/bug Something isn't working

Comments

@kwannoel
Copy link
Contributor

kwannoel commented Apr 30, 2024 •
edited
Loading

PG:

> create table ...

CREATE TABLE

RisingWave:

> create table ...

CREATE_TABLE

Have extra underscore 🤣
@github-actions github-actions bot added this to the release-1.9 milestone Apr 30, 2024
@kwannoel kwannoel added priority/low type/bug Something isn't working and removed type/feature labels Apr 30, 2024
@kwannoel kwannoel changed the title Minor: Mismatch in PG and RW frontend output for CREATE xx Minor: Mismatch in PG and RW frontend output for DDL statements, should have whitespace rather than underscore delimiters Apr 30, 2024
@kwannoel kwannoel changed the title Minor: Mismatch in PG and RW frontend output for DDL statements, should have whitespace rather than underscore delimiters bug: Mismatch in PG and RW frontend output for DDL statements, should have whitespace rather than underscore delimiters Apr 30, 2024
@kwannoel kwannoel removed this from the release-1.9 milestone Apr 30, 2024
@xiangjinwu
Copy link
Contributor

might be related: #14007

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jul 3, 2024

This issue has been open for 60 days with no activity.
If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.
You can also confidently close this issue as not planned to keep our backlog clean. Don't worry if you think the issue is still valuable to continue in the future. It's searchable and can be reopened when it's time. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
no-issue-activity priority/low type/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xiangjinwu @kwannoel