-
Notifications
You must be signed in to change notification settings - Fork 391
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
InternalServerError
when not using a variable defined in with
in a query
#6279
Comments
It used to be, but we started allowing it in 3.0. |
As a workaround, until this is fixed, wrapping the second insert in a |
The problem was cardinality inference wasn't getting run on it. If the body of the WITH was something other than an INSERT, cardinality inference happened somewhat by accident, since multiplicity inference was done properly. Fixes #6279.
The problem was cardinality inference wasn't getting run on it. If the body of the WITH was something other than an INSERT, cardinality inference happened somewhat by accident, since multiplicity inference was done properly. Fixes #6279.
The problem was cardinality inference wasn't getting run on it. If the body of the WITH was something other than an INSERT, cardinality inference happened somewhat by accident, since multiplicity inference was done properly. Fixes #6279.
The problem was cardinality inference wasn't getting run on it. If the body of the WITH was something other than an INSERT, cardinality inference happened somewhat by accident, since multiplicity inference was done properly. Fixes #6279.
Not sure if it's exactly the same but in many cases if i declare a variable inside a Example:
|
Could you give an example query with the schema that you are using? This should not be happening, we need to fix it. |
3.4+301ba34
EdgeDB CLI 3.5.0+907ff37
Steps to Reproduce:
This triggers the following error:
The expected behavior is that the syntax error (?) should be identified and warned against.
(?): Is it a syntax error to not use a variable, like it is in Go? Or is this not meant to be an error at all?
Either way, the error is resolved by using the
parent
variable to fill in theparent_post
property of the second insert toPost
.The text was updated successfully, but these errors were encountered: