8000 Risingwave is not able to parse the some INTERVAL query · Issue #7059 · risingwavelabs/risingwave · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Risingwave is not able to parse the some INTERVAL query #7059

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
Closed
Tracked by #6640
sushantgupta opened this issue Dec 26, 2022 · 2 comments
Closed
Tracked by #6640

Risingwave is not able to parse the some INTERVAL query #7059

sushantgupta opened this issue Dec 26, 2022 · 2 comments
Assignees
@BowenXiao1999
Labels
type/bug Type: Bug. Only for issues.
Milestone
release-0.1.15

Comments

@sushantgupta
Copy link

Describe the bug

In PostgreSQL:

todwvwql=> SELECT '1 mons 1 days 00:00:01.000001'::INTERVAL; 
        interval
-------------------------
 +0-1 +1 +0:00:01.000001
(1 row)

todwvwql=> SELECT '1 mons 1 days 00:00:00.000001'::INTERVAL; 
        interval
-------------------------
 +0-1 +1 +0:00:00.000001
(1 row)

todwvwql=>

In Rising wave:

dev=> SELECT '1 mons 1 days 00:00:01.000001'::INTERVAL; --working fine
       ?column?
----------------------
 1 mon 1 day 00:00:01
(1 row)

dev=> SELECT '1 mons 1 days 00:00:00.000001'::INTERVAL; --here is the issue
ERROR:  QueryError: Expr error: Parse error: risingwave_common::types::interval::IntervalUnit
dev=>

To Reproduce

No response

Expected behavior

No response

Additional context

No response
@sushantgupta sushantgupta added the type/bug Type: Bug. Only for issues. label Dec 26, 2022
@sushantgupta sushantgupta added this to the release-0.1.15 milestone Dec 26, 2022
@lmatz lmatz mentioned this issue Dec 27, 2022
Open
65 tasks
@fuyufjh
Copy link
Collaborator
fuyufjh commented Dec 28, 2022

@ZENOTME Can you please take a look today? We hope to fix this in release-0.1.15

@fuyufjh fuyufjh assigned BowenXiao1999 and unassigned ZENOTME Dec 28, 2022
@BowenXiao1999
Copy link
Contributor

Draft a pr that should close this for now: #7096

however, The value will lost because we use miliseconds in IntervalUnit, this one is microseconds level. we should fix this after #4514, but now seems it is untracked in our plan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BowenXiao1999 BowenXiao1999

Labels
type/bug Type: Bug. Only for issues. < 4006 /div>
Projects
None yet
Milestone
release-0.1.15
Development

No branches or pull requests
4 participants
@sushantgupta @fuyufjh @BowenXiao1999 @ZENOTME
0