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

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • in reply to: #25719
    Alex
    Member

    Hi,

    the tests with v 6.16beta1 are proceed well. No crash occurs anymore by the conditions as described in this thread.

    It's fine that the rows from complete deleted privileges (procs/functions) entries are now cleaned up in the table procs_priv.

    All listed bugs in this thread are now fixed.

    Thank you.

    in reply to: #25731
    Alex
    Member
    Mahesh wrote on Jan 24 2008, 02:39 PM:
    Please Check and let us know the details,

    Thanks

    Hi Mahesh,

    all listed bugs in this thread are now fixed with V6.16beta1.

    Thank you for it.

    in reply to: #25715
    Alex
    Member

    Hi Peter,

    I have researched a little bit too on how it can be that a user must have global select privileges.

    So I studied the refman on Mysql and the mysql database.

    Of course, the user doesn't need to have global select privileges.

    That also would be a security risk at all.

    It is because I work with two accounts in the same table (test table).

    In this case I created accidental a procedure with the root account and mysql sets definer logically to 'root@localhost'.

    Normal it should be 'test@localhost'.

    When the backup is executed it has accordingly no rights to access the stored procedure which was created with the definer 'root@localhost'.

    Now the crash occurs.

    It is also with views an functions.

    We can say if the backup has the wrong privileges on views, functions and stored procs it crashes.

    I think this is helpful for you to circle the problem and reproduce the crash.

    I see that you get the same results like I.

    Your are rigth that the the 'grantor' column is not used at the moment (RefMan 5.1).

    I agree that some things should be done by the server itself.

    I use 5.0.45 MySQL Community Server 5.0.45 Windows.

    I haven't yet checked the changelog for 5.0.51. Hope that a windows binary is available soon.

    Chris

    in reply to: #25710
    Alex
    Member

    Hi,

    here are some results from testing.

    I now can reproduce the crash. It occurs when the user has no global select privileges.

    If you don't have a database with stored procs, views and maybe functions the backup works fine.

    If you have any of these stored procs,views or functions and you don't have global select privileges it crashes.

    I don't know if it is a Mysql problem or not. I think that it can't be that an user must have global select privileges to backup a database

    which contains a view or a stored procedure.

    However that is what I have found. It still happens in V6.16 b1 n.

    Another bug shows me when I observe the mysql database specifically the table procs_priv.

    When you create a new stored procedure and then set the privileges (manage permissions) for that, it writes down the routine type incorrectly.

    I see function instead of procedure. When I changed it twice than the routine type is correct.

    Append: Sri, I see the that the routine_type bug already confirmed. It works correctly with V6.16 b1 n

    Another thing is when I delete the permissions for the stored_proc . It deletes only the value in field proc_priv not the hole row.

    On the side, the grantor field is always empty.

    in reply to: #25709
    Alex
    Member

    Hi there,

    some new info about the problem.

    Today I try to execute the backup with stored procedures again and it crashes again.

    And I believe now why.

    It is because the test-user has a privilege problem.

    When I backup as root it works when I backup as test-user it crashes.

    I am still confused because the user TEST has all privileges for his Database.

    The difference from root and testuser is that root has global privileges for all and testuser

    only all privilegs for the database “test”.

    I am still testing and let you know if I have more information about it.

    in reply to: #25728
    Alex
    Member
    Mahesh wrote on Jan 18 2008, 04:12 PM:
    HI,

    We have fixed the issue,Please verify the fix with this 6.16(Not released) build .

    To download,

    http://www.webyog.com/downloads/betas/not_…QLyog616Ent.exe

    Hi Mahesh,

    thanks for the effort. I have tested it with “V 6.16 b1 n” and it works now correctly.

    But there was another problem I have found.

    Append: This problem is also in V 6.15.

    When I update a value in the result, save them and immediately export these updated result the content differs.

    The export content is correct by csv, html, xml but when I export it with the formats excel-xml and sql it gives me the unchanged values.

    I will explain it by an example:

    Test table:

    ID value

    1 A

    2 B

    3 C

    Query: select * from test;

    Result:

    ID value

    1 A

    2 B

    3 C

    Update value from ID 2 B –> test

    Save changes

    Now export to Format: csv,html,xml

    Result:

    ID value

    1 A

    2 test

    3 C

    Now export to Format excel xml,sql

    Result:

    ID value

    1 A

    2 B

    3 C

    It seems that csv, html, xml now involved. Therefore exactly vice-versa to the prior problem.

    By the way in V 6.15 updates in the result are saved automatically when I select another row in the result, so I remember that.

    It isn't in this Version.

    Chris

    in reply to: #25725
    Alex
    Member
    peterlaursen wrote on Jan 15 2008, 02:32 PM:
    hello … and it is me too 🙂

    Please tell the exact program version that you use!

    If it is not 6.15 then please try this one. There was such issue fixed recently!

    It is definitive 6.15 the latest Version (Enterprise Edition)

    Please note that I found this problem only by the formats html, xml and csv !

    Excel XML and SQL are not involved.

    Chris

    in reply to: #25707
    Alex
    Member
    peterlaursen wrote on Jan 15 2008, 01:20 PM:
    Did you reboot the OS in between? Maybe the system memory was corrupted somehow when this crash occurrred?

    The last reboot was on 13.1 at 11:30 (same day).

    The crash occurs later in the evening.

    Since there the computer runs 24/7 hours without rebooting.

    When I at home today I will try to reconstruct this case.

    At the time I am at work

    in reply to: #25705
    Alex
    Member
    peterlaursen wrote on Jan 14 2008, 10:10 AM:
    Also the crash dump might be useful!

    Thanks for reply.

    It is momentary one little strange.. Today I try to repeat the crash but it doesn't do.

    I have nothing changed since this problem occurs.

    Normal I am testing such problems in various kinds before posting for help.

    I don't know what happens.

    For testingt purpose I have attached the neccessary files you wanted.

Viewing 9 posts - 1 through 9 (of 9 total)