Celine Wüst

I just noticed that this bug no longer triggers already since version 5.9.0! Is it safe to close this issue as completed?

Thanks for looking into this @safi50 and @waleedahmed0001. However, this doesn't seem like it solves the problem. Removing the `n0` identifier in the query lets the query run successfully. Additionally,...

`gdb` stacktrace: ``` #0 0x000055766192b3d8 in datumTransfer () #1 0x00005576617bdef4 in SPI_datumTransfer () #2 0x00007f1581ec5610 in plpgsql_exec_function () from /usr/lib/postgresql/13/lib/plpgsql.so #3 0x00007f1581ed0dd3 in plpgsql_call_handler () from /usr/lib/postgresql/13/lib/plpgsql.so #4 0x00005576617832e2 in...

`gdb` stacktrace: ``` #0 0x00007f158d9c2d16 in epoll_wait (epfd=4, events=0x5576629cb6b0, maxevents=1, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 0x00005576618ce67c in WaitEventSetWait () #2 0x00005576617cae30 in secure_read () #3 0x00005576617d2947 in ?? () #4 0x00005576617d37e5...

Hello! I wanted to quickly ask if this bug is fully fixed now or not, since there seem to be a few commits addressing it?

Thanks for looking into this @jrgemignani! This query was run against an empty database, I have edited the issue such that this is evident. Since the error arises on the...

Thanks for looking into this @AviAvni! However, I believe that the query I reported doesn't contain an importing `WITH` statement. The error also disappears if I remove the `ORDER BY`...

But the following query seems to work and returns 1? ```cypher WITH 0 AS x CALL { WITH 1 AS y RETURN y AS y } RETURN y ```

Hi @swilly22! Yes, I do, though it's currently closed-source. I'll let you know once it's open-sourced though, if you want to!