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

ODBC Import Mapping

forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › ODBC Import Mapping

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • July 20, 2005 at 10:00 pm #9118
      rbma
      Member

      This field 'BT_ID' is unchecked under the Transform window yet the following error is generated.

      DBMS Information: MICROSOFT SQL SERVER

      Importing table schema: Name…

      ERROR: 1072, Key column 'BT_ID' doesn't exist in table

      Thanks.

    • July 20, 2005 at 10:13 pm #18663
      peterlaursen
      Participant

      it reads

      Quote:
      Key column 'BT_ID' doesn't exist in table

      and not

      Quote:
      column 'BT_ID' doesn't exist in table

      Is there any other columns selected having some sort of relationsship with column BT_ID ??

      Sounds like it tries to create a FK with mySQL to a column that is not there!!

      If there is another column selected using BT_ID for a FK did you uncheck “import FK” option behind the “advanced” button?

      If that is it, I won't consider it a bug … though I have proposed that selection and unselection of FKs and indexes should be “more visible” ….

      But the new things with ODBC import and SQLyog 4.1 are:

      1) scheduling

      2) import of “metadata” ( = “data about data” ie. FK's and indexes)

      3) it is MUCH faster

    • July 20, 2005 at 10:22 pm #18664
      rbma
      Member

      Yes, that was it. Thank you. 😀

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