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

bug(expr): to_char consider unsupported format as plain text #14670

Open
KeXiangWang opened this issue Jan 19, 2024 · 2 comments
Open

bug(expr): to_char consider unsupported format as plain text #14670

KeXiangWang opened this issue Jan 19, 2024 · 2 comments
Assignees
Labels
no-issue-activity type/bug Something isn't working

Comments

@KeXiangWang
Copy link
Contributor

Describe the bug

Current, to_char works like this:

  1. find all the format item like 'YYYY(means year)'
  2. replace them with the number
  3. if the format item is unrecognized, consider it as plain text and keep it unchaged.
  4. return the string after replacemnt

The problem happens in 3. As we haven't support all the format item. An unknown format item will be kept as plain text and outputed. It does not produce any errors. This may cause user confused. Throwing an error may be better.

Error message/log

wrong output: `Day`

To Reproduce

SELECT to_char('2015-09-01T14:48:05.359000'::timestamp, 'Day');

Expected behavior

output Tuesday

How did you deploy RisingWave?

doesn't matter.

The version of RisingWave

v1.6

Additional context

No response

@KeXiangWang KeXiangWang added the type/bug Something isn't working label Jan 19, 2024
@github-actions github-actions bot added this to the release-1.7 milestone Jan 19, 2024
@fuyufjh
Copy link
Member

fuyufjh commented Mar 6, 2024

Ping @KeXiangWang

Copy link
Contributor

github-actions bot commented Aug 1, 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. 😄

@KeXiangWang KeXiangWang removed this from the release-1.10 milestone Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants