You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@age.apache.org by "aru-d-at (via GitHub)" <gi...@apache.org> on 2023/05/02 23:32:22 UTC

[GitHub] [age] aru-d-at commented on issue #871: Using CALL with a function and a RETURN with an undefined variable does not output correct error

aru-d-at commented on issue #871:
URL: https://github.com/apache/age/issues/871#issuecomment-1532277970

   @jrgemignani 
   
   > `ERROR:  Procedure call inside a query does not support naming results implicitly`
   This error is far more descriptive to me as it underlines that `YIELD` is required after a `CALL` clause when I require the results to be named.
   
   Seems like, in the case the user is making a solo `CALL` and wants to return the vertex they would need to use the `CALL ... YIELD` syntax. I have now found that queries like
   ```pgsql
   SELECT * FROM cypher('test', $$
       MATCH (v) WHERE v.name='J' CALL toInteger(v.customer_id) RETURN a
   $$) as (v agtype);
   ```
   and
   
   ```pgsql
   SELECT * FROM cypher('test', $$
       MATCH (v) WHERE v.name='J' CALL toInteger(v.customer_id) RETURN v
   $$) as (v agtype);
   ```
   
   Both return the same error.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@age.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org