Drizzled Public API Documentation

slave::ReplicationSchema Class Reference
Inheritance diagram for slave::ReplicationSchema:
slave::SQLExecutor

Public Member Functions

bool create ()
bool setInitialMaxCommitId (uint32_t master_id, uint64_t value)
bool createInitialApplierRow (uint32_t master_id)
bool createInitialIORow (uint32_t master_id)
void markInErrorState ()
void clearErrorState ()
const std::string & getErrorMessage () const
bool executeSQL (std::vector< std::string > &sql)

Protected Attributes

drizzled::Session::shared_ptr _session

Detailed Description

Definition at line 28 of file replication_schema.h.

Member Function Documentation

bool slave::SQLExecutor::executeSQL ( std::vector< std::string > &  sql)
inherited

Execute a batch of SQL statements.

Parameters
sqlBatch of SQL statements to execute.
Return values
trueSuccess
falseFailure

Definition at line 49 of file sql_executor.cc.

bool slave::ReplicationSchema::setInitialMaxCommitId ( uint32_t  master_id,
uint64_t  value 
)

Set initial value of the last applied COMMIT_ID value in applier_state.

This is used when the server is started with –slave.max-commit-id to begin reading from the master transaction log at a given point. This method will persist the value to the applier_state table. If it wasn't permanently stored immediately, we risk the possibility of losing the value if the server is again restarted without ever having received another event from the master (which causes persistence of the value). An edge case, but still possible.

Parameters
[in]master_idUnique master identifier.
[in]valueThe initial value.

Definition at line 174 of file replication_schema.cc.

Referenced by slave::ReplicationSlave::initWithConfig().


The documentation for this class was generated from the following files: