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

Automatic Foreign Key Naming

forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Automatic Foreign Key Naming

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • June 18, 2009 at 7:56 am #29156
      peterlaursen
      Participant

      I think it will be difficult across sessions. But can't you leave it empty and the server will name the constraint? I will have to refresh my mind about it.

    • June 18, 2009 at 1:15 pm #29157
      garethwatson
      Member
      peterlaursen wrote on Jun 18 2009, 08:56 AM:
      I think it will be difficult across sessions. But can't you leave it empty and the server will name the constraint? I will have to refresh my mind about it.

      Its populated by default with the FK_. Honestly, I have not tried blanking the field and seeing what happens. I will give it a go and let you know.

      As for it being difficult across sessions, I am unsure what that means. Are you saying that two people creating the same foriegn key with the same name at the same time?

      Thanks for the reply,

      Gareth.

    • June 19, 2009 at 5:02 pm #29158
      DonQuichote
      Member

      I can really recommend not being “lazy” and providing a name yourself. That name is then not dependent on the tool you use and consistent across servers (so your update / upgrade scripts will work consistently). I would not like SQLyog to be inconsistent with MySQL. If you do not give a name, MySQL provides one in a consistent fashion. I would not want that process hijacked by my database frontend.

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