DBRE - User's manual

/ English / Russian /

Table of contens:

1. Description of application
2. How it works
3. Command line options
4. Configuration file
5. Extensions of source database

Configuration file

The configuration file is XML format and contains the following sections:
<replication> - base section

<input> - section of the input data source. On the whole configuration file should be in the singular..
It has a parameter type which can primat value file or db
Depending on the parametr value the section <input> should contain the following subsections:
For file:
<name> - path to file. Example: /var/dbre/exchange/enterprise_database.lre
For db:
<type> - RDBMS type. It can take values: fb, mysql, oracle, odbc, postgre, sqlite
<server> - IP address or dns name of the server database
<database> - database name
<user> - database user
<password> - user password
<role> - The role of the user. Only RDBMS fb
<charset> - Charset. In accordance with the agreement for the selected database.

<output> - section of the output data source. Similarly <input>

<deleted> - section - the key. It may contain 1 or 0, and also absent. It is designed to activate unloading / loading of information on the deleted data. When the setting, the source database should contain a table deletedfields (More see Extensions of source database)

<table> - section containing parameters unloading table. It may be present in any quantity (number needed to replicate the tables). It shall contain the following subsections:
<input_name> - table name in data source
<output_name> - table name in destination
<unloaded> - section - the key. It may contain 1 or 0 and also absent. Includes control regime unloading. When the regime in the source-database table must be present field unloaded (More see Extensions of source database). Unloaded only record the value NULL in this field. After discharge, they shall be 1.

<field> - section contains the parameters of table fields. It may be present in the section <table> in any quantity.
<input_name> - field name in the table data source
<output_name> - field name in the table data destination
<type> - type of field. It may take the following values:
int
float
double
string - by default
date
time
timestamp
blob
<index> - pointer that field is the key. It can take values 1, 0 or missing. To identify the records in the destination-database, for its renewal.
<autoinc> - pointer that field is the autoincrement. It can take values 1, 0 or missing. When enabled a field is not entered in the table of the receiver.

Example of configuration file

<?xml version="1.0" ?>
<replication>
    <input type="file">
	<name>/var/dbre/exchange/test.lre</name>
    </input>
    <output type="db">
        <type>fb</type>
        <server>localhost</server>
        <database>testdb</database>
        <user>SYSDBA</user>
        <password>masterke</password>
    </output>
    <deleted>1</deleted>
    <table>
        <input_name>table1</input_name>
        <output_name>table1</output_name>
        <unloaded>1</unloaded>
	<field>
	    <input_name>id</input_name>
	    <output_name>id</output_name>
	    <type>int</type>
	    <index>1</index>
	    <autoinc>1</autoinc>
	</field>
        <field>
            <input_name>field11</input_name>
            <output_name>field11</output_name>
            <type>string</type>
        </field>
        <field>
	    <input_name>field12</input_name>
	    <output_name>field12</output_name>
	    <type>timestamp</type>
	</field>
	<field>
            <input_name>field13</input_name>
            <output_name>field13</output_name>
	    <type>int</type>
        </field>
    </table>
    <table>
        <input_name>table2</input_name>
	<output_name>table2</output_name>
	<field>
	    <input_name>id1</input_name>
	    <output_name>id1</output_name>
	    <type>int</type>
	    <index>1</index>
	</field>
	<field>
	    <input_name>id2</input_name>
	    <output_name>id2</output_name>
	    <type>int</type>
	    <index>1</index>
	    <autoinc>1</autoinc>
	</field>
	<field>
	    <input_name>field21</input_name>
	    <output_name>field21</output_name>
	    <type>int</type>
	</field>
	<field>
            <input_name>field22</input_name>
            <output_name>field22</output_name>
            <type>string</type>
        </field>
        <field>
            <input_name>field23</input_name>
            <output_name>field23</output_name>
            <type>int</type>
        </field>
    </table>
</replication>

Extensions of source database

For additional features such as control unloaded and deleted records in the source-database the following additions should be made:
1. All table entries are to be monitored for unloading, should be added field unloaded:

alter table TABLE1 add UNLOADED char(1);

To reset the field at the time of recording the changes in the table you want to add a trigger for an event update:

create trigger TABLE1_BU0 for TABLE1
active before update position 0
as
begin
    if (new.UNLOADED = old.UNLOADED) then
	new.UNLOADED = null;
end

2. For unloading information on deleted records in the database you want to add table deletedfields:

create table DELETEDFIELDS (TEXT varchar(255));

For the record, its data in each table must be controlled by adding a trigger to an event before delete:

create trigger TABLE1_BD0 for TABLE1
active before delete position 0
as
begin
    insert into DELETEDFIELDS (TEXT) values ('TABLE1;ID:'||cast(old.ID as varchar(10))||';');
end

Trigger must enter the line to read: TABLE_NAME;KEY_FIELD_NAME1:VALUE;KEY_FIELD_NAMEN:VALUE;