aru-d-at commented on issue #871: URL: https://github.com/apache/age/issues/871#issuecomment-1532201739
@jrgemignani So, after further investigating the issue, I have found that the crash by itself is unrelated to the `CALL` clause. Rather, it seems using AGE 1.3.0 on a Database that had previously used AGE 1.1.0 results in crashing the database. Most queries seem to cause a crash. When I opened the issue, my database was in a a similar state (AGE 1.1.0 -> 1.3.0) and it just so happens the query used at the time had the `CALL` clause. For this issue, the title as well as the error output needs to be edited. So I will do that first. In regards to the crash, it can be either be that, 1.3.0 is incompatible with 1.1.0 based Databases or that it is indeed a bug. I may need to open a separate issue for this. For the PR, I was working on the master branch and therefore switched to PG11 with a fresh database. It utilised the master branch installation all through the database initialisation as well as testing. As such, the crash did not occur there, instead I did get the error message as it is currently implemented. `ERROR: Procedure call inside a query does not support naming results implicitly` Referring to a similar clause used in Neo4j it does not match the error message. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
