Get desktop application:
View/edit binary Protocol Buffers messages
* Deallocate already prepared statement @startuml client -> server: Deallocate alt Success client <- server: Ok else Failure client <- server: Error end @enduml @returns @ref Mysqlx::Ok or @ref Mysqlx::Error
* client side assigned statement id, must be already prepared
* Execute already prepared statement @startuml client -> server: Execute alt Success ... Resultsets... client <- server: StmtExecuteOk else Failure client <- server: Error end @enduml @returns @ref Mysqlx::Ok
Used in:
* client side assigned statement id, must be already prepared
* Arguments to bind to the prepared statement
* send only type information for @ref Mysqlx::Resultset::ColumnMetaData, skipping names and others
* Prepare a new statement @startuml client -> server: Prepare alt Success client <- server: Ok else Failure client <- server: Error end @enduml @returns @ref Mysqlx::Ok or @ref Mysqlx::Error
* client side assigned statement id, which is going to identify the result of preparation
* defines one of following messages to be prepared: Crud::Find, Crud::Insert, Crud::Delete, Crud::Upsert, Sql::StmtExecute
Used in:
Determine which of optional fields was set by the client (Workaround for missing "oneof" keyword in pb2.5)
Used in: