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

Gui Bug (insert Only Granted User, "item")

forums forums SQLyog SQLyog: Bugs / Feature Requests Gui Bug (insert Only Granted User, "item")

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • #9399
      neuro
      Member

      user is only granted insert rights to DB

      when connected try to expand a table details

      after receiving the expected error about insufficient rights a new item named “Item” appears at the bottom of the objects explorer

      definitely minor, but in case it hides st bigger…

      Thanks for a great product

    • #20012
      peterlaursen
      Participant

      I can reproduce this with MySQL 5.0 and 5.1 . See attached. Here user 'tttt' has insert privilege only to database 'test2'.

      The icon is a table icon. But not placed in a database tree!! It stands alone!

      And it does not not seem to be a graphical display error only , because when trying to

      Code:
      alter table test2.item add column peter bigint;

      mysql returns

      Quote:
      ALTER command denied to user 'tttt'@'localhost' for table 'item'

      Trying on table test

      Code:
      alter table test.item add column peter bigint;

      returns

      Quote:
      Table 'test.item' doesn't exist

      .

      However opening another connection as root does not find any test2.item or just item DB. 5. Also the database test2 does not show up at all when a similar setup is crated with MySQL version 4.0 or 4.1 (unless it is InnoDB!)

      It is a harmless phenomenon, I believe, but never the less some kind of small bug with SQLyog in relation to MySQL 5.x – or a small bug just only visible in MySQL 5.

      Pics:

      Left: phenomenon displayed in MySQL 5.

      Mid: MySQL 4 – nothing is dispalyed as user has no select privilege at all.

      Right: MySQL 3.23 displays this err mess when trying to open table tree.

      The different behaviour(s) of 3.23 and 4.0 is a know issue with the respective MySQL version and tables with no SELECT-privilege..

      However wasn't MySQL 5 expected to behave like 4.x ?

    • #20013
      Ritesh
      Member

      Added to our bug-list. Will be fixed in v5.1.

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