|
Contents
Index
<< Previous
Next >>
PDF
Synchronize
|
|
Menu: Extras / Synchronize
MySQL-Front allows the synchronization of different tables. The primary index is used to identify the data. This means that tables can be synchronized only with a primary index.
The objects of the table(s) (fields / indices) are identified with the column names.
Foreign keys are not transferred during the synchronization.
You can synchronize two different tables on different (or the same) session.
Otherwise it's possible to synchronize two databases or two entire sessions. But it's not recommended to synchronize two sessions, since this encloses the "mysql" database.
What:
| Either the data structure (objects) and/or the data can be synchronized.
|
Direction:
| Only the table(s) identified as slaves are modified.
|
Update existing objects:
| The settings (e.g. data type) of existing object is updated.
|
Existing data:
| Existing data are updated (overwritten) without any warning.
|
Ignore Foreign Keys:
| Foreign keys are deactivated during synchronization. Please consult the MySQL manual for a description of advantages and disadvantages of this functionality.
|
Lock Tables:
| A table being synchronized is locked to other users / programs during the synchronization process. Please consult the MySQL manual for a description of advantages and disadvantages of this functionality.
|
Backup:
| A table can be generated before synchronizing data. This table will be assigned the name of the respective table with the extension "_bak". Already existing copies with this extension are overwritten without warning.
|
| A backup copy is generated completely within the database. Creating backups can use significant resources of the database if tables are large.
|
Warning:
Existing data are changed during synchronization and cannot be restored.
User or program errors are always a possibility.
Data backups are therefore important and should be created frequently!
See also:
|
|
