Set default blob parameters
Client
Int32—p_operation-
Operation code (
op_batch_set_bpb—106) Int32—p_batch_statement-
Statement handle
Buffer—p_batch_blob_bpb-
Default BLOB parameter buffer
Int32 — p_operationOperation code (op_batch_set_bpb — 106)
Int32 — p_batch_statementStatement handle
Buffer — p_batch_blob_bpbDefault BLOB parameter buffer
Int32 — p_operationOperation code (op_batch_regblob — 104)
Int32 — p_batch_statementStatement handle
Int64 — p_batch_exist_idExisting BLOB ID
Int64 — p_batch_blob_idBatch temporary BLOB ID
|
Caution
|
This description needs further verification and possibly correction.For example, it seems to mix up Buffer and Byte[].We’re also not able to match some fields to the implementation.For example, the repeated "Record length" seems to be absent, or may actually refer to the |
Int32 — p_operationOperation code (op_batch_blob_stream)
Int32 — p_batch_statementStatement handle
Buffer[] — p_batch_blob_dataBLOB stream
This stream is a sequence of blob records.Each blob records contains:
UInt32Record length
The following three fields are called BLOB header
Int64Batch temporary BLOB ID
UInt32BLOB size
UInt32BLOB parameters buffer size
BufferBLOB parameters buffer
BufferBLOB data (length - BLOB size bytes) (what does this mean?)
BLOB headers and records in a stream need not match, i.e. one record may contain many BLOBs and BLOB may stretch from one record to next.
Uses the [wireprotocol-requests-info] message with:
p_operation
|
|
p_info_object
|
Statement handle |
p_info_items
|
Values of |
Attach to a service.Use message [wireprotocol-connect-attach] with op_service_attach — 82.
p_atch_file:Current Firebird versions only support one service: service_mgr.Since Firebird 3.0, this can also be an empty string (empty buffer) with the same meaning.
Send [wireprotocol-connect-detach] with op_service_detach — 83, followed by [wireprotocol-connect-disconnect].
Although the message looks similar to [wireprotocol-requests-info], it has different semantics.
Int32 — p_operationOperation code (op_service_start — 85)
Int32 — p_info_objectUnused, always use 0
Int32 — p_info_incarnationIncarnation of object (0)
TODO: Usage and meaning?
Buffer — p_info_itemsService parameter buffer
Although the message looks similar to [wireprotocol-requests-info], it has different semantics.
Int32 — p_operationOperation code (op_service_info — 84)
Int32 — p_info_objectUnused, always use 0
Int32 — p_info_incarnationIncarnation of object (0)
TODO: Usage and meaning?
Buffer — p_info_itemsService parameter buffer
Buffer — p_info_recv_itemsRequested information items
Int32 — p_info_buffer_lengthRequested information items buffer length
[wireprotocol-responses-generic] — on success, p_resp_data contains the requested information.