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

No PRIMARY KEY bug?

forums › forums › SQLyog › Sync tools, Migration, Scheduled Backup and Notifications › No PRIMARY KEY bug?

  • This topic is empty.
Viewing 4 reply threads
  • Author
    Posts
    • March 16, 2005 at 9:20 pm #17183
      Ritesh
      Member

      Please provide complete description of your setup. Versions of MySQL, SQLyog and whether you are using tunneling.

      Can you send me a backup of your db?

    • March 16, 2005 at 9:52 pm #17184
      gh0st
      Member

      I am using two mysql servers version 4.1.10, both running on seperate servers running fedora core 2 linux

      I am not using tunneling

      I am using SQLyog job agent 4.0 on the primary sql server, running fedora core 2 linux

      i cannot readily send a dump of our db as it contains passwords, i can send a dump of one of the tables which does infact have a primary key (in which sja reports that it does not)

      if that would be enough, where would you like me to send the dump?

    • March 16, 2005 at 10:55 pm #17185
      Ritesh
      Member
      Quote:
      i can send a dump of one of the tables which does infact have a primary key (in which sja reports that it does not)

      Send to ritesh AT webyog DOT com

    • March 16, 2005 at 11:14 pm #17186
      Ritesh
      Member

      I received your SQL file. The table structure looks like:

      CREATE TABLE `virtual` (

      col1,

      col2, col3,

      UNIQUE KEY `col` (`col1`)

      }

      If you notice then the key is UNIQUE but not PRIMARY. You have to explicitly define PRIMARY KEY for the table. SQLyog does not support UNIQUE KEY as of now.

    • March 16, 2005 at 11:40 pm #17187
      gh0st
      Member

      so, its a feature then, not a bug

      thanks 😉

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