Classes
AbstractQueryProtocolMessage
Abstract base class for extended query protocol messages. These can be buffered in memory locally until a flush or sync message is received. Any corresponding database statement will only be executed once a flush/sync is received.
BindMessage
Message of type bind (meaning that it is a message called to a prepared statement to complete it with missing data to prepare for execution). A bound prepared statement always yields a portal unless it fails.
BootstrapMessage
This represents all messages which occur before ControlMessage type messages. Those include encryption, admin (e.g.: cancellation) and start-up messages.
CancelMessage
This message handles the imperative cancellation, as issues in a new connection by the PG wire protocol. We expect that this message contains an ID for the connection which issues the original query, as well as an auth secret.
CloseMessage
Close the designated statement.
ControlMessage
Generic representation for a control wire message: that is, a message which does not handle any form of start-up, but reather general communications.
CopyDataMessage
Normally used to send data to the back-end. Spanner does not currently support this, so send will throw a descriptive error to be sent to the user. Note that we do parse this in order for this to be future proof, and to ensure the input stream is flushed of the command (in order to continue receiving properly)
CopyDoneMessage
Normally used to signal a copy command is done. Spanner does not currently support copies, so send will throw a descriptive error to be sent to the user. Note that we do parse this in order for this to be future proof, and to ensure the input stream is flushed of the command (in order to continue receiving properly)
CopyFailMessage
Normally used to signal a copy command failed. Spanner does not currently support copies, so send will throw a descriptive error to be sent to the user. Note that we do parse this in order for this to be future proof, and to ensure the input stream is flushed of the command (in order to continue receiving properly)
DescribeMessage
Calls describe on a portal or prepared statement.
ExecuteMessage
Executes a portal.
FlushMessage
Handles a flush command from the user. JDBC does not require this step, so server-side this is a noop.
FunctionCallMessage
Normally used to send a function call the back-end. Spanner does not currently support this, so send will throw a descriptive error to be sent to the user. Note that we do parse this in order for this to be future proof, and to ensure the input stream is flushed of the command (in order to continue receiving properly)
ParseMessage
Creates a prepared statement.
PasswordMessage
A Password Message takes a username and password and input and supposedly handles auth. Here, however, since connections are through localhost, we do not do so.
QueryMessage
Executes a simple statement.
SSLMessage
Handles SSL bootstrap message. Since we do not do SSL (connection is expected to be through localhost after all), we decline the first message, and send an error for subsequent ones.
StartupMessage
The first (non-encryption, non-admin) message expected in from a client in a connection loop. Here we handle metadata and authentication if any.
SyncMessage
Handles a sync command from the user. JDBC does not require this step, so server-side this is a noop.
TerminateMessage
Closes a connection.
WireMessage
Generic representation for a wire message, generally executed by calling send.
Enums
ControlMessage.ManuallyCreatedToken
Token that is used to mark ControlMessages that are manually created to execute a QueryMessage.