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

Elements in Empty List Resolving to STRING by Default Causes Issues #2874

Closed
mxwli opened this issue Feb 13, 2024 · 1 comment
Closed

Elements in Empty List Resolving to STRING by Default Causes Issues #2874

mxwli opened this issue Feb 13, 2024 · 1 comment
Assignees
Labels
frontend Frontend, i.e., binder, parser, query planning-related issues

Comments

@mxwli
Copy link
Collaborator

mxwli commented Feb 13, 2024

If we write a query like this:

UNWIND $idList as tid MATCH (t:tag {id: tid}) RETURN t;

Where id expects an INT64 type, the query runs fine on a non empty $idList. However, when we have idList = [], then the query gives

Expression tid has data type STRING but expected INT64. Implicit cast is not supported.
@mxwli mxwli added the frontend Frontend, i.e., binder, parser, query planning-related issues label Feb 13, 2024
@mxwli mxwli assigned mxwli and andyfengHKU and unassigned mxwli Feb 13, 2024
@andyfengHKU
Copy link
Contributor

Should be fixed in #3374

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
frontend Frontend, i.e., binder, parser, query planning-related issues
Projects
None yet
Development

No branches or pull requests

2 participants