Classes
AcceptSSLResponse
Signals to client that we accept SSL.
AuthenticationCleartextPasswordResponse
AuthenticationOkResponse
Assures the client that the authentication process (if any) was successful.
BindCompleteResponse
Assures to the client that a statement got bound to a portal successfully.
CloseCompleteResponse
Assures to the client that a portal got closed successfully.
CloseResponse
Assures to the client that a portal got closed successfully.
CommandCompleteResponse
Signals to a client that an issued query is complete.
CopyDataResponse
CopyDoneResponse
CopyInResponse
CopyOutResponse
DataRowResponse
Sends to the client specific row contents.
DeclineSSLResponse
Signals to client that we do not accept SSL.
EmptyQueryResponse
ErrorResponse
Sends error information back to client.
KeyDataResponse
Sends back information regarding the current connection (identifier and secret) as part of start-up. Used for cancel statements.
MD5AuthenticationRequest
Used for password response.
NoDataResponse
Signals the end of a describe statement.
NoticeResponse
Notices can be sent as asynchronous messages and can include warnings, informational messages, debug information, etc.
ParameterDescriptionResponse
Response (with data) for describe statement.
ParameterStatusResponse
Sends back start-up parameters (can be sent more than once)
ParseCompleteResponse
Signals the end of a parse transaction.
PortalSuspendedResponse
Signals that there are more rows available.
ReadyResponse
Signals readiness status to receieve messages (here we only tend to send Idle, which means ready)
RowDescriptionResponse
Sends back qualifier for a row.
StartUpMessageResponse
Sends back start-up parameters (can be sent more than once)
TerminateResponse
Signals the end of a connection.
WireOutput
Classes inheriting WireOutput concern themselves with sending data back to the client using PG wire protocol. These classes function similarly to com.google.cloud.spanner.pgadapter.wireprotocol.WireMessage in that they use the constructor to instantiate items, but require send to be called to actually send data. Here, you must override postSend with data you wish to send. Note that this subclass will handle sending the identifier and length (provided you initialize them correctly through getIdentifier and he constructor respectively) via send, so you just have to implement payload sending.
Enums
CopyDataResponse.ResponseType
NoticeResponse.NoticeSeverity
ReadyResponse.Status
Status of the session.