Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Row Based 2-Way Synchronization

forums › forums › SQLyog › Using SQLyog › Row Based 2-Way Synchronization

  • This topic is empty.
Viewing 1 reply thread
  • Author
    Posts
    • December 20, 2010 at 3:34 pm #31723
      peterlaursen
      Participant

      Your understanding that 'source will overwrite target' for rows with a PK-conflict is correct . There also is no option for such user interaction as requested.

      The advice I use to give in this situation is to avoid PK conflicts in such cases by adding one more (new) column to the PK on every table. This column should be constant on same server but different on different servers.

    • December 21, 2010 at 12:25 pm #31724
      Kribor
      Member
      'peterlaursen' wrote:

      The advice I use to give in this situation is to avoid PK conflicts in such cases by adding one more (new) column to the PK on every table. This column should be constant on same server but different on different servers.

      That's not possible for us since we are using this as a part of our release process. We edit existing entries (already has a primary key) on our Release Candidate, test it and then deploy the DB to prod DB. Whereas the Prod Db some rows might have been “quick-fixed” in the meantime so we can't overwrite everything.

      So it seems we are out of luck…

  • Author
    Posts
Viewing 1 reply thread
  • You must be logged in to reply to this topic.