Problems with synchronization

Without any doubt, synchronization or two way replication exposes the most problems of all replication models.

To name a few:

  • Duplicates key conflicts
  • Update conflicts
  • Delete conflicts
  • Remote delete (with or without partitioning)
  • Restrictive trigger action
  • Additive trigger action
  • Constraints blocking operations

Most of these problem must be solved in the application it self. Frext cannot handle most of these issues, they must be solved during implementation or better: during design of the implementation. Some problems cannot be solved technically, but must be solved by procedures or restricting access to certain actions.