Fix docs for QueryExecModeDescribeExec with connection poolers
https://github.com/jackc/pgx/issues/1635
This commit is contained in:
@@ -585,8 +585,10 @@ const (
|
|||||||
QueryExecModeCacheDescribe
|
QueryExecModeCacheDescribe
|
||||||
|
|
||||||
// Get the statement description on every execution. This uses the extended protocol. Queries require two round trips
|
// Get the statement description on every execution. This uses the extended protocol. Queries require two round trips
|
||||||
// to execute. It does not use prepared statements (allowing usage with most connection poolers) and is safe even
|
// to execute. It does not use named prepared statements. But it does use the unnamed prepared statement to get the
|
||||||
// when the the database schema is modified concurrently.
|
// statement description on the first round trip and then uses it to execute the query on the second round trip. This
|
||||||
|
// may cause problems with connection poolers that switch the underlying connection between round trips. It is safe
|
||||||
|
// even when the the database schema is modified concurrently.
|
||||||
QueryExecModeDescribeExec
|
QueryExecModeDescribeExec
|
||||||
|
|
||||||
// Assume the PostgreSQL query parameter types based on the Go type of the arguments. This uses the extended protocol
|
// Assume the PostgreSQL query parameter types based on the Go type of the arguments. This uses the extended protocol
|
||||||
|
|||||||
Reference in New Issue
Block a user