Hello! There is a website, there is a common (main) database (in the General Login Database picture), and there are, say, 2-3 other databases that work with similar (identical) identification data but contain additional fields that are unique only for these databases (in the pictures these are Login Database 1 and L. db 2, marked in red).

This is all located on 2-3 different servers. The user cannot change the identification data through the "General DB". The question is how to synchronize databases in one direction. That is, if there is a change in General, then all these changes are sent or queued for sending (the remote server may be offline) in Log.DB1, Log.DB2, etc.?

I use: ubuntu 16.04 mysql 5.7 MyISAM table type

Shows sync direction

  • one
    Move the block of data to be synchronized to a separate database and configure unidirectional replication of this database. If cascade operations (including triggers) are not tied to this data, then you can not create a separate database and restrict yourself to replication of individual tables (well, that is, you can do this anyway, but more dreary). Accordingly, each table with data for replication (both on the master and on the slave) will have to be divided into two with a 1: 1 connection — in the replicated fields alone, in the second only non-replicating fields. - Akina
  • Thanks seems to fit, it turned out so masterdb-> slavedb -> table-replications with a pair of necessary columns-> triggers -> live table with extra fields. - Amaroc

0