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

Feature Request

forums › forums › SQLyog › Sync tools, Migration, Scheduled Backup and Notifications › Feature Request

  • This topic is empty.
Viewing 5 reply threads
  • Author
    Posts
    • September 22, 2005 at 8:46 pm #9245
      shawn_h
      Member

      In my opinion:

      it would be nice for SJA to provide a list of duplicated rows in case of an auto incremented PK row. Further, it should provide a mechanism for the user to allow duplicated rows from one database be inserted in the other in one and/or two way synchronization. The option to enforce data entegrity should be left to the administrator not the software; however the functionality and the means should exist.

      I still think the product is very nice though and I have already paid and used the enterprise version.

    • September 22, 2005 at 9:01 pm #19265
      peterlaursen
      Participant
      Quote:
      a list of duplicated rows in case of an auto incremented PK row

      Dublicated rows simply can't exist if there is a PK. The server prevents this! At least the value of the PK differs for each row!

      Please explain!

      And BTW: I'll play it back now 😀

      auto incremented PK row >>> must be >>> auto incremented PK column

      (information for others: Shawn PM'ed me a note about a row/column mismatch in one of my articles!)

    • September 23, 2005 at 3:53 am #19266
      Ritesh
      Member

      Can you provide an example to explain the issue a little more?

    • September 23, 2005 at 3:26 pm #19267
      shawn_h
      Member
      Ritesh wrote on Sep 22 2005, 11:53 PM:
      Can you provide an example to explain the issue a little more?

      [post=”7285″]<{POST_SNAPBACK}>[/post]

      Sure can! If two databases are being synced up and in the first db in one table there is a field that is a PK but the same field in the second table is not a PK, then, the software should allow for the update in a one way situation to the second database's table.

    • September 23, 2005 at 3:28 pm #19268
      shawn_h
      Member
      peterlaursen wrote on Sep 22 2005, 05:01 PM:
      Dublicated rows simply can't exist if there is a PK.  The server prevents this! At least the value of the PK differs for each row!

      Please explain!

      Right on! that's exactly why you'd want to see a list of duplicated rows; to determine what to do with them, if anything. Maybe, the admin decides to change something and update the target.

      Does this make sense?

    • September 24, 2005 at 6:51 am #19269
      Ritesh
      Member

      I have added your request in the TO-DO list. Though I cannot guarantee you which version of SQLyog will have this feature.

  • Author
    Posts
Viewing 5 reply threads
  • You must be logged in to reply to this topic.