ensembl-hive
2.8.0
|
This RunnableDB module lets you copy/merge rows from a table in one database into table with the same name in another. There are three modes ('overwrite', 'topup' and 'insertignore') that do it very differently. Also, 'where' parameter allows to select subset of rows to be copied/merged over.
Definition at line 21 of file MySQLTransfer.pm.
protected Bio::EnsEMBL::Hive::RunnableDB::MySQLTransfer::_assert_same_table_schema | ( | ) |
Undocumented method
public Bio::EnsEMBL::Hive::RunnableDB::MySQLTransfer::fetch_input | ( | ) |
Description : Implements fetch_input() interface method of Bio::EnsEMBL::Hive::Process that is used to read in parameters and load data. Here it parses parameters, creates up to two database handles and finds the pre-execution row counts filtered by '$where'.
param('src_db_conn'): connection parameters to the source database (if different from hive_db)
param('dest_db_conn'): connection parameters to the destination database (if different from hive_db - at least one of the two will have to be different)
param('mode'): 'overwrite' (default), 'topup' or 'insertignore'
param('where'): filter for rows to be copied/merged.
param('table'): table name to be copied/merged.
param('lock_tables'): [boolean] when 1, lock tables when dumping the source database. Default if not set (or set to 0) is to not lock (runs mysqldump with --skip-lock-tables)
public Bio::EnsEMBL::Hive::RunnableDB::MySQLTransfer::get_row_count | ( | ) |
Undocumented method
public Bio::EnsEMBL::Hive::RunnableDB::MySQLTransfer::param_defaults | ( | ) |
Undocumented method
public Bio::EnsEMBL::Hive::RunnableDB::MySQLTransfer::write_output | ( | ) |
Description : Implements write_output() interface method of Bio::EnsEMBL::Hive::Process that is used to deal with job's output after the execution. Here we compare the number of rows and detect problems.