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

v4.0.6 RC1 – SQL dump, Error 1146

forums forums SQLyog SQLyog: Bugs / Feature Requests v4.0.6 RC1 – SQL dump, Error 1146

  • This topic is empty.
Viewing 5 reply threads
  • Author
    Posts
    • #9026
      larsen
      Participant

      Hello,

      when I have a DB selected and then open the sql dump menu, whatever DB I choose afterwards is ignored and SQLYog can´t find the table:

      – select DB “test1”

      – open menu tools, export database as sql dump

      – in the database selection select DB “test2”

      – select any table

      – click on export

      –> Error No.: 1146

      Table 'test2.example' doesn´t exist

      Lars

    • #18027
      peterlaursen
      Participant

      From Laursen to Larsen …

      Hi!

      I never heard abut anything like it! I can't repoduce anything like it!

      Could it be that the user that you log on with has only the SHOW_DB privilege but not the SELECT privilege ??

      Please try to logon as “ROOT” or some “admin” user (with the highest privilege that you can get )and repeat !

      If you use the predefined user “test” he has only orivilges to to the “test” database and NOT “test2” or anything else unless you have changed it!

      Is it a locally installed MySQL or at som webhosting ?? And what is the MySQL version ?

      And the host from where you connect is defined correctly with the user ? (unless you specify otherwise user is only allowed to connect from “localhost” – that how MySQL works).

      Do you experience the same problem with otehr applications ??

      If you have updated your MySQL-version from a previous version did you remmeber to update the GRANT-tables ?

      I believe you are Danish so you might write in Danish if you want …

    • #18028
      peterlaursen
      Participant

      I see in another post of yours that it is mySQL 4.1.12, son u don't need to answer this!!

      Can you show data in the data-pane and result-pane ???

    • #18029
      larsen
      Participant
      Quote:
      From Laursen to Larsen …

      🙂

      Quote:
      Could it be that the user that you log on with has only the SHOW_DB privilege but not the SELECT privilege ??

      no. logged in as user root on a mysql server 4.1.12-max (installed via rpm) on our intranet.

      Quote:
      If you use the predefined user “test” he has only orivilges to  to the “test” database and NOT “test2” or anything else unless you have changed it!

      Sorry, I had better chosen another name. I didn´t mean the predefined test db.

      Quote:
      And the host from where you connect is defined correctly with the user ?  (unless you specify otherwise user is only allowed to connect from “localhost” – that how MySQL works).

      Everything else works fine.

      When I choose the DB I want to sqldump before I select the menu item it´s ok.

      It´s just when I select another DB in the sql dump screen that I get this error.

      Quote:
      I believe you are Danish so you might write in Danish if you want …

      Sorry, but my Danish is not that good as I´m German 😉

      'Larsen' is my nick for 'Lars' – a Nordic name anyway 😎

    • #18030
      peterlaursen
      Participant

      OK I can reproduce it now just like …

      Code:
      /*
      SQLyog Enterprise v4.06 RC1
      Host – 5.0.6-beta-nt-max : Database – test
      *********************************************************************
      Server version : 5.0.6-beta-nt-max
      */

      create database if not exists `test`;

      USE `test`;

      Now you write

      Quote:
      When I choose the DB I want to sqldump before I select the menu item it´s ok.

      It´s just when I select another DB in the sql dump screen that I get this error.

      That makes things perfectly clear! I did not get that point until now. I always sqldump from right-clicking on a DB or a table, so I never ran into it myself!

      Well .. yes … it must be categorized as an error with the program … but not critical for me.

    • #18031
      Ritesh
      Member

      Bug confirmed.

      It will be fixed in v4.07.

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