You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a pgsql_connection:extended_query of the form
INSERT INTO address (v, acct_id, org_id,)
VALUES ( $1, $2, $3)
RETURNING id;
The return value is e.g. {{insert, 0, 1}, {[{record, <<00,08....>>}]}}
I.e. the return value is not decoded from the raw binary as it is for a SELECT query.
Using pgsql_connection:simple_query instead, gives e.g. {{insert, 0, 1}, {[{21}]}}
It would be great to be able to use the set and return pattern as it eliminates one DB round trip.
The text was updated successfully, but these errors were encountered:
I am confused as there are tests with pgsql_connection:extended_query (or param_query which calls extended_query eventually) and INSERT ... RETURNING ... queries.
I believe there might be some problem with the decoding of the type of data you are returning, as decoding goes through two different paths whether the query is extended or simple, closely matching PostgreSQL protocol. Could you please provide a more complete case?
For a
pgsql_connection:extended_query
of the formINSERT INTO address (v, acct_id, org_id,)
VALUES ( $1, $2, $3)
RETURNING id;
The return value is e.g.
{{insert, 0, 1}, {[{record, <<00,08....>>}]}}
I.e. the return value is not decoded from the raw binary as it is for a
SELECT
query.Using
pgsql_connection:simple_query
instead, gives e.g.{{insert, 0, 1}, {[{21}]}}
It would be great to be able to use the set and return pattern as it eliminates one DB round trip.
The text was updated successfully, but these errors were encountered: