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

Error No. 1216

  • This topic is empty.
Viewing 5 reply threads
  • Author
    Posts
    • #10419
      jlamarque
      Member

      Hello,

      despite the fact I put in my xml file, I have this message in my log when I synchronize 2 databases

      Error No. 1216 Cannot add or update a child row: a foreign key constraint fails

      Have you got any solution for me ?

      Thanks for advance,

    • #24406
      peterlaursen
      Participant

      “I have this message in my log” .. you are sure this is not an old message?

      will not check for FK

      will do reverse

      .. so you should not have this!

      If the problem is as described we will need a more detailed test case (tables + jobfile).

      You can create a ticket with the details if you don't want to expose here.  You may also 'fake' passwords etc.

    • #24407
      jlamarque
      Member

      I have always this message and some of my lines don't be synchronized.

      I put my xml file in attachment.

      Maybe it's because of my old mysql version (4.1.9) ?

    • #24408
      peterlaursen
      Participant

      I cannot tell if ther is sosme bug with InnoDB in that specific MySQL version!

      basically MySQL 4.1 before 4.1.12 should ALWAYS be upgraded!

      We need a SQL-dump of the tables too.  And consider using the ticket system and not the Forums!  I also think you have exposed a little too much details in that XML you posted!

    • #24409
      jlamarque
      Member

      So, I advance in my tests, I now work with MySql 4.1.22, and I conclude that the problem comes from the http tunnel.

      In fact, I test the same synchronisation without (it works fine) and with the tunnel (the foreign key constraint fails appear in the yogtunnel.log).

      Have you an idea (My SqlYog version is 5.21) ?

      Thanks

      peterlaursen wrote on Jun 29 2007, 09:52 AM:
      I cannot tell if ther is sosme bug with InnoDB in that specific MySQL version!

      basically MySQL 4.1 before 4.1.12 should ALWAYS be upgraded!

      We need a SQL-dump of the tables too. And consider using the ticket system and not the Forums! I also think you have exposed a little too much details in that XML you posted!

    • #24410
      peterlaursen
      Participant

      As always we request that you test issues with the latest available stable SQLyog version!

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