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

Database Synchronization Wizard

forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Database Synchronization Wizard

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • September 6, 2006 at 3:02 pm #22320
      peterlaursen
      Participant

      did you check the 'SET FOREIGN_KEYS_CHECK = 0″ box?

      http://dev.mysql.com/doc/refman/5.0/en/set-option.html

      Quote:
      FOREIGN_KEY_CHECKS = {0 | 1}

      If set to 1 (the default), foreign key constraints for InnoDB tables are checked. If set to 0, they are ignored. Disabling foreign key checking can be useful for reloading InnoDB tables in an order different from that required by their parent/child relationships. See Section 14.2.6.4, “FOREIGN KEY Constraints”.

      Actually 'circular references' are possible and then there is NO TABLE ORDER 'that saves the day' !

      The Foreign_keys_check option is for that.

    • September 6, 2006 at 3:21 pm #22321
      peterlaursen
      Participant

      Also the 'mysqldump' program uses this.

      From http://dev.mysql.com/doc/refman/5.0/en/inn…onstraints.html

      Quote:
      To make it easier to reload dump files for tables that have foreign key relationships, mysqldump automatically includes a statement in the dump output to set FOREIGN_KEY_CHECKS to 0. This avoids problems with tables having to be reloaded in a particular order when the dump is reloaded.

      I always mismatch this 🙁

      Correct is “FOREIGN_KEY_CHECKS”, “FOREIGN_KEYS_CHECK” is wrong!

    • September 6, 2006 at 4:59 pm #22322
      TGKnIght
      Member

      Ah oops… I had seen the option but did not know what it was for.. Will test it out in a little while.

      Thanks!

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