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

Sync Not Correct

forums forums SQLyog SQLyog: Bugs / Feature Requests Sync Not Correct

  • This topic is empty.
Viewing 10 reply threads
  • Author
    Posts
    • #12238
      maxhugen
      Participant

      A number of times. with different MySQL dbs, I have sync'd from the server to my dev pc – but, a [seemingly] random table does NOT match in terms of numbers of records.

      This is one example:

      Image4.png

      I just don't know what to make of this. If anyone can point to some info re this, I'd sure welcome it!

      MTIA

    • #31873
      peterlaursen
      Participant

      Are you using a DOUBLE/FLOAT column for the PK? Please paste SHOW CREATE TABLE output for the table.

      Also please tell the SQLyog version.

    • #31874
      maxhugen
      Participant

      Hi Peter

      I'm using SQLyog v8.71

      The table is:

      CREATE TABLE `changetracking` (

      `ChangeTrackingID` int(11) NOT NULL AUTO_INCREMENT,

      `DocID` int(11) NOT NULL,

      `TrackingReason` varchar(50) NOT NULL,

      `From_PeopleID` int(11) NOT NULL,

      `From_Title` varchar(50) DEFAULT NULL,

      `To_PeopleID` int(11) NOT NULL,

      `To_Title` varchar(50) DEFAULT NULL,

      `To_Representing` varchar(50) DEFAULT NULL,

      `To_Capacity` varchar(50) DEFAULT NULL,

      `To_SortOrder` smallint(4) DEFAULT NULL,

      `ApproveMin` decimal(15,4) DEFAULT NULL,

      `ApproveMax` decimal(15,4) DEFAULT NULL,

      `DateSent` datetime DEFAULT NULL,

      `DateReceived` datetime DEFAULT NULL,

      `ts` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,

      PRIMARY KEY (`ChangeTrackingID`),

      KEY `DocID` (`DocID`),

      KEY `From_PeopleID` (`From_PeopleID`),

      KEY `To_PeopleID` (`To_PeopleID`),

      CONSTRAINT `changetracking_ibfk_1` FOREIGN KEY (`From_PeopleID`) REFERENCES `apppeople` (`appPeopleID`) ON UPDATE CASCADE,

      CONSTRAINT `changetracking_ibfk_2` FOREIGN KEY (`To_PeopleID`) REFERENCES `apppeople` (`appPeopleID`) ON UPDATE CASCADE,

      CONSTRAINT `changetracking_ibfk_3` FOREIGN KEY (`DocID`) REFERENCES `changedocs` (`DocID`) ON DELETE CASCADE ON UPDATE CASCADE

      ) ENGINE=InnoDB AUTO_INCREMENT=2147324833 DEFAULT CHARSET=utf8

    • #31875
      peterlaursen
      Participant

      Is there some other application using the table while sync is running?

    • #31876
      maxhugen
      Participant

      It is possible, but I have tested the sync at various times during the day and night (US), and it's the same.

    • #31877
      peterlaursen
      Participant

      OK .. it looks like it is data-specific then.

      Is it possible for you to share the table with us? Or just a subset of the table where it is reproducible?

    • #31878
      peterlaursen
      Participant

      Please also tell your MySQL version(s). I note decimal(15,4) types. One possibility could be a server issue with such type.

    • #31879
      maxhugen
      Participant

      Peter, is there a way to do a 'dump' of just one table? I can certainly send you the data as it is not sensitive, and cannot be identified to the client. I guess you would need both the production table data and my dev data (which I sync to)?

      The MySQL versions are:

      Server: 5.1.51-community

      My development machine: 5.1.40-community

      Thank you.

    • #31880
      peterlaursen
      Participant

      To dump a single table with SQLyog just right-click it in the Object Browser. Next select “Backup/Export >> Backup Table as SQL dump”. Select “structure and data” option and for our convenience uncheck the option to add a USE statement.

      Please do from both databases, name files unambiguously (like “source.sql” + “target.sql” for instance). next zip the two files into a single zip-archive.

      You can create a support ticket by sending a mail to [email protected]. Attach the .zip to the mail and put a link to this post here so that we can identify it.

    • #31881
      peterlaursen
      Participant

      We have replied in your ticket.

    • #31882
      maxhugen
      Participant

      Thanks very much – working AOK now! 😎

Viewing 10 reply threads
  • You must be logged in to reply to this topic.