Public

<init>

Finishes a copy operation and unlocks connection discarding any exchanged data.

cancelCopy

doSubprotocolBegin

Finishes writing to copy and unlocks connection.

endCopy

flushCopy

hasLock

Locks connection and calls initializer for a new CopyOperation Called via
startCopy -> processCopyRe

initCopy

interpretCommandStatus

Obtain lock over this connection for given object, blocking to wait if
necessary.

lock

Handles copy sub protocol responses from server. Unlocks at end of sub protocol,
so operations on pg

processCopyResults

processDeadParsedQueries

processDeadPortals

processResults

Blocks to wait for a row of data to be received from server on an active copy
operation Connection g

readFromCopy

receiveAsyncNotify

receiveCommandStatus

receiveErrorResponse

receiveFastpathResult

receiveFields

receiveNoticeResponse

QueryExecutorImpl

Making http post requests using okhttp

Thrown when a file specified by a program cannot be found.

java.io.FileNotFoundException

An immutable arbitrary-precision signed decimal.A value is represented by an
arbitrary-precision "un

java.math.BigDecimal

Produces concatenated messages in language-neutral way. New code should probably
use java.util.Forma

java.text.MessageFormat

A plug-in replacement for JDK1.5 java.util.Hashtable. This version is based on
org.cliffc.high_scale

java.util.Hashtable

org.hamcrest.core.IsNull

The LoggerFactory is a utility class producing Loggers for various logging APIs,
most notably for lo

org.slf4j.LoggerFactory

setContentView

getContentResolver

requestLocationUpdates

// nb: if we decide to use a portal (usePortal == true) we must also use a named statement

// (oneShot == false) as otherwise the portal will be closed under us unexpectedly when

// Work out how many rows to fetch in this pass.

// We're discarding any results anyway, so limit data transfer to a minimum

// Not using a portal -- fetchSize is irrelevant

// fetchSize > maxRows, use maxRows (nb: fetchSize cannot be 0 if usePortal == true)

// Must do this after sendParse to pick up any changes to the

// Only supply type information when there isn't any

// already, don't arbitrarily overwrite user supplied

// A statement describe will also output a RowDescription,

// so don't reissue it here if we've already done so.

"Simple mode does not support describe requests. sql = "

"Queries that might contain ; must be executed with QueryExecutor.QUERY_EXECUTE_AS_SIMPLE mode. "

// Per https://www.postgresql.org/docs/current/static/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY

// A Bind message can use the unnamed prepared statement to create a named portal.

// If the Bind is successful, an Execute message can reference that named portal until either

//      the end of the current transaction

//   or the named portal is explicitly destroyed

// the usePortal flag controls whether or not we use a *named* portal

/*
       * don't send describe if we already have cached the row description from previous executions
       *
       * XXX Clearing the fields / unpreparing the query (in sendParse) is incorrect, see bug #267.
       * We might clear the cached fields in a later execution of this query if the bind parameter
       * types change, but we're assuming here that they'll still be valid when we come to process
       * the results of this query, so we don't send a new describe here. We re-describe after the
       * fields are cleared, but the result of that gets processed after processing the results from
       * earlier executions that we didn't describe because we didn't think we had to.
       *
       * To work around this, force a Describe at each execution in batches where this can be a
       * problem. It won't cause more round trips so the performance impact is low, and it'll ensure
       * that the field information available when we decoded the results. This is undeniably a
       * hack, but there aren't many good alternatives.
       */

How to use sendBindmethodin org.postgresql.core.v3.QueryExecutorImpl

Best Java code snippets using org.postgresql.core.v3.QueryExecutorImpl.sendBind (Showing top 4 results out of 315)

How to use
sendBind
method
in
org.postgresql.core.v3.QueryExecutorImpl