Parsing failure in extended query protocol

[emotionbug]

Hello.

i trying to use AGE with JDBC.

and, i faced failure when Message Flow is extended query mode with CREATE clause.
has any solution with this issue or guide?

cheers.

failure query

SELECT * from cypher('my_graph_name', $$
  CREATE (a:Part {part_num: '123'}), 
         (b:Part {part_num: '345'}), 
         (c:Part {part_num: '456'}), 
         (d:Part {part_num: '789'})
$$) as (a agtype);

error message

Type : Error
Length : 98
Severity: ERROR
Code: XX000
Message: unrecognized node type : -1944838080
File : copyfuncs.c
Line: 5658
Routine: copyObjectImpl

environment
Docker : sorrell/agensgraph-extension-alpine

Cheers.

reference link : https://www.postgresql.org/docs/12/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY

[JoshInnis]

Hello,

Judging from the reference link you attached, I am assuming you are using prepared statements in Postgres' JDBC driver. Is this correct?

Unfortunately, the CREATE clause is not currently compatible with prepared statements, even if there are no params passed to the Cypher section of the query. We are looking to add this feature in future releases.

[emotionbug]

Yes, but it just happened on statement too.
because, Postgres JDBC's default Message Flow is extended mode.
not in Simple query mode like Node.js or Python.

OK. thank you for replying. :)

[jrgemignani]

I will see if I can reproduce the error and see if there might be an oversight in the copyfuncs.c library. john

…

On Mon, Mar 1, 2021 at 9:30 PM Alex Kwak ***@***.***> wrote: Yes, but it just happened on statement too. because, Postgres JDBC's default Message Flow is extended mode. not in Simple query mode like Node.js or Python. OK. thank you for replying. :) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALPO4BU6MO2HOQMO3L5BJLTBRZVXANCNFSM4YN6XKNA> .

[jrgemignani]

Josh is correct. I did not find anything that was an oversight. john

…

On Tue, Mar 2, 2021 at 9:27 AM John Gemignani ***@***.***> wrote: I will see if I can reproduce the error and see if there might be an oversight in the copyfuncs.c library. john On Mon, Mar 1, 2021 at 9:30 PM Alex Kwak ***@***.***> wrote: > Yes, but it just happened on statement too. > because, Postgres JDBC's default Message Flow is extended mode. > not in Simple query mode like Node.js or Python. > > OK. thank you for replying. :) > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#28 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AALPO4BU6MO2HOQMO3L5BJLTBRZVXANCNFSM4YN6XKNA> > . >

[Remi-C]

Having the same problem folks.
I'm using the Open source DBeaver to run my queries, and I can not create a graph properly.
It works when using psql though.
DBeaver also works when running data querying that does not involves changing the data.
This is a big problem for us, as our users won't use the command line / psql under any circumstances.

Workaround : I'm thinking about writing a wrapper in Plpython that runs query inside a bash terminal.
That is pretty ugly though.

[JoshInnis]

Hi Remi,

This issue is about creating vertices and edges. Is that the issue you are having or can you not create a graph at all in DBeaver?

[Remi-C]

Hey @JoshInnis , thanks for answering :-)
I just followed exactly the query from the doc:

SELECT * from cypher('my_graph_name', $$
  CREATE (a:Part {part_num: '123'}), 
        (b:Part {part_num: '345'}), 
        (c:Part {part_num: '456'}), 
        (d:Part {part_num: '789'})
$$) as (a agtype);

The previous queries worked fine (create extension, set search path, create graph object, ...)

[JoshInnis]

We are working on a fix for this right now. I was able to recreate the issue with DBeaver and will test to verify the fix works there as well.

[Remi-C]

Wow you work fast folks !
I was very interested by the seminar today, I'm super curious to use this extension with medium to large graphs and see what I can do with it.

[JoshInnis]

Hi @emotionbug the JDBC driver is now compatible with Prepared Statements.

@Remi-C, we also tested on DBeaver and the patch should make that compatible to. Btw, glad to hear you enjoyed the presentation.

[Remi-C]

Thanks @JoshInnis !
Can I simply pull on master to try it, or do I have to use a specific branch / tag?

[JoshInnis]

Currently this patch is only in master.

[emotionbug]

I tested it then, this issue is solved.

Thanks @JoshInnis and, @jrgemignani.