Embedded Files
All communication between Vertica clients and servers is done through discrete packets. Request packets are sent by clients, response packets are sent by Vertica servers.
For full details, consult the Vertica documentation.
All packets have the following properties:
packetType (string): the type of the packet, e.g. "Query", "BindComplete" or "DataRow" - read only
toString (function): returns a short description of the packet
toLongString (function): returns a longer description of the packet
The packet types most commonly used in user logic are: Query, Parse, Bind, DataRow, and RowDescription.
Request packets
Request packets
Bind: sent to provide values for the parameters of a prepared statement
Close: sent to close a prepared statement
CopyData: used for COPY LOCAL
CopyDoneRequest: used for COPY LOCAL
CopyError: signals an error with a COPY LOCAL
CopyFail: signals a failure with a COPY LOCAL
Describe: requests a description of a prepared statementÂ
EndOfBatchRequest: signals the end of data for a batch insert
Execute: requests execution of a prepared statement
Flush: requests a flush
MarsRequest: requests a Multiple Active ResultSets session
Parse: starts a prepared statement
PasswordResponse: sends the user's password (rarely used)
Query: executes a SQL query
StartupMessage: initiates a connection
Sync: syncs up with the server
Terminate: closes the connection to the server
VerifiedFiles: used as part of batch inserts
Response packets
Response packets
AuthenticationRequest: requests authentication from the client
BackendKeyData: information required to cancel a request
BindComplete: signals completion of a prepared statement bind
CloseComplete: signals completion of the closing of a prepared statement
CommandComplete: signals the completion of a command
CommandDescription: information about a prepared statement
CopyData: used for COPY LOCAL
CopyDoneResponse: used for COPY LOCAL
CopyInResponse: used for COPY LOCAL
DataRow: a row in a result set
EmptyQueryResponse: response to an empty query
EndOfBatchResponse: signals the end of a batch operation
ErrorResponse: returns an error to the client
LoadBalanceResponse: used on connect for load balancing
LoadFile: used for batch operations
MarsResponse: used for Multiple Active Result Set sessions
NoData: signals that the requests resulted in no data
NoticeResponse: a notice to the client
ParameterDescription: describe the parameters for a prepared statement
ParameterStatus: returns the current value of a parameter
ParseComplete: signals that a prepared statement has been parsed
PortalSuspended: signals that a prepared statement has been suspended
ReadyForQuery: signals that the server is ready
RowDescription: description of a result set
VerifyFiles: requests the client to provide batch data
WriteFile: a response to COPY FROM LOCAL
Google Sites
Report abuse