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
Would this have an impact on performance or server resources?
pqDescribePrepared gives you the columns of the result schema. That lets us infer the schema without the current SELECT (*) LIMIT 0 hack, which breaks down for things that aren't SELECTs.
The text was updated successfully, but these errors were encountered:
Before we tried to infer the query schema before COPY by wrapping
it in a "SELECT * FROM (...) LIMIT 0". This broke if the query
was (for example) a CREATE or UPDATE. Instead, use a prepared
statement to infer instead. If we find that there are no result
columns, then execute without the COPY path.
Also, test what happens with "INSERT INTO ... RETURNING" (this
works with COPY).
Fixesapache#701.
Before we tried to infer the query schema before COPY by wrapping it in
a "SELECT * FROM (...) LIMIT 0". This broke if the query was (for
example) a CREATE or UPDATE. Instead, use a prepared statement to infer
instead. If we find that there are no result columns, then execute
without the COPY path.
Also, test what happens with "INSERT INTO ... RETURNING" (this works
with COPY).
Fixes#701.
Would this have an impact on performance or server resources?
pqDescribePrepared gives you the columns of the result schema. That lets us infer the schema without the current
SELECT (*) LIMIT 0
hack, which breaks down for things that aren't SELECTs.The text was updated successfully, but these errors were encountered: