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

Forum Replies Created

Viewing 15 posts - 3,331 through 3,345 (of 7,398 total)
  • Author
    Posts
  • in reply to: #25754
    peterlaursen
    Participant

    please tell:

    1) Which of the monitors is PRIMARY and which is SECONDARY monitor?

    2) Which one is LEFT and which one is RIGHT positioned?

    3) Is the Multimonitor setup using some specific driver utility or the basic Windows functionalities only?

    4) There is no way to tell the system that the monitor will be disconnected before disconnecting it physically?

    5) Is SQLyog behaving differently that other programs in this respect?

    We fixed some multimonitor issues about 1 year ago, but now I do not remember every detail! Let us try to recall and maybe have a brief look at the code!

    in reply to: Tunnelling On Shared Host: Extension Xml Was Not Found #23678
    peterlaursen
    Participant

    hmm ……

    I agree that this is not very impresssing how GoDaddy supports a product (in case SQLyog) that is distributed through their own channels.

    We will discuss tomorrow morning how to handle this.

    in reply to: #25738
    peterlaursen
    Participant

    Also you posted in the MONyog category! I will move you out of here (to the SQLyog category!) 🙂

    in reply to: #25737
    peterlaursen
    Participant

    Please tell the program version you are using.

    A brief test here (6.15 and latest 'not_released' 6.16 build) did not reproduce it like you reported!

    in reply to: #25716
    peterlaursen
    Participant
    Quote:
    mysql sets definer logically to 'root@localhost'

    We should not crash under any circumstance! Now tomorrow morning we will find the exact position in the code where this occurs and fix it!

    in reply to: #25714
    peterlaursen
    Participant

    Actually SQLyog crashes with the (non-scheduled) export with the same conditions!

    [attachment=813:morecrash.gif]

    in reply to: #25713
    peterlaursen
    Participant

    crash easily reproducable with this simple setup:

    [attachment=812:crash.gif]

    Grants for umtest@localhost


    GRANT USAGE ON *.* TO 'umtest'@'localhost'

    GRANT EXECUTE, ALTER ROUTINE ON FUNCTION `umtest`.`untest1` TO 'umtest'@'localhost'

    Server is 5.0.45.

    Function can be anything – here it is only

    CREATE DEFINER=`root`@`localhost` FUNCTION `untest1`() RETURNS int(11)

    BEGIN

    return 77;

    END$$

    After granting SELECT privilege on the `mysql`database there is no crash! Actually different MySQL versions behave differently with the `mysql`database – so this may be a recent change in the server where we did not adjust our code appropriately! We should check for that condition and handle the exception gracefully at least!

    in reply to: #25712
    peterlaursen
    Participant

    I have been researching a little into 4) above

    When every checkbox for a function in 'manage permissions' is unchecked we send SQL like

    (both database, user and SF is named 'umtest' with this example)

    — this will clear the table

    delete from mysql.procs_priv where user='umtest' and host='localhost';

    — we need a little additional info that we retrieve from information_schema

    select `specific_name`,`routine_type` from `information_schema`.`routines` where `routine_schema` = 'umtest' and routine_type = 'PROCEDURE'|'FUNCTION' and `specific_name` = 'umtest';

    — now we populate the table with whatever information user left in the 'manage permissions' GUI and the name and type of the routine as retrieved

    insert into mysql.procs_priv(host, db, user, routine_name, routine_type, grantor, proc_priv) values ('localhost', 'umtest', 'umtest', 'umtest', 'FUNCTION', '', '');

    — flush to take effect permanently

    flush privileges;

    I think you have point! When the `proc_priv` column is '' (empty string) there is no

    idea to insert any row at all! Here the INSERT statment may be skipped – and that will leave

    the privilege table less messy! But still it is a small detail in my opinion!

    Also the 'grantor' column is not populated either, as you reported! I do not think it matters much but we should insert exactly what the GRANT statement does! This will require a little research in MySQL docs, change-logs, bug reports etc

    in reply to: #25711
    peterlaursen
    Participant

    1) we will test the crash with lack of GLOBAL privileges on Monday (2row)

    2) “I don't know if it is a Mysql problem or not.” A crash is always a problem with the application. If some MySQL error is involved, SQLyog should not crash but return an appropriate error message! Anyway please tell the exact server version!

    3) “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.” Will be checked in detail 2row too!

    4) “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.” It is designed like that. And I think it is a 'weakness' with the MySQL privilege system/implementation itself. Such 'cleanup' should be done by the server!

    Another similar example is that if a user has DELETE (for instance) privilege to a table and is granted DELETE privilege to the database where the table belongs the privilege to the table is 'redundant' and makes no sense anymore. Also this I think should (might be optional) be cleaned up by the server.

    Yet another example is that is user has a privilege to an object (database, table – whatever) and the object is dropped, the privilege remains in the `mysql`database!

    A utility to remove empty, redundant and depreciated privileges would be nice! We might add to SQLyog one day – though it rather should be done by MySQL AB (and ideally in the server itself as an optional parameter to 'flush privileges' or something like that)

    5) “On the side, the grantor field is always empty.” Maybe that column was added to `mysql` after our code was written! We will check details!

    Thanks – Your detailed reports are much appreciated!

    in reply to: #25708
    peterlaursen
    Participant

    any news here? did you experience this crash again?

    in reply to: #25734
    peterlaursen
    Participant

    Please tell:

    What MONyog version are you using? 1.51? Windows version or … ?

    This is a browser error message I think. What browser? IE .. Firefox or … ? Did you try another?

    Could there be any kind of firewall issue involved? Are you connecting from a browser running on the same machine as where MONyog is installed or from another computer?

    I think you could easily get the same error mesage if you try to connect from the browser to a non-existent domain?

    Basically I think there must be something that prevents/blocks connection!

    in reply to: #25729
    peterlaursen
    Participant
    Quote:
    When I update a value in the result, save them and immediately export these updated result the content differs…with the formats excel-xml and sql it gives me the unchanged values.

    Confirmed. Will be fixed too of course! Thanks for persistence!

    in reply to: #25724
    peterlaursen
    Participant

    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!

    in reply to: #25706
    peterlaursen
    Participant

    Did you reboot the OS in between? Maybe the system memory was corrupted somehow when this crash occurrred?

    in reply to: #25696
    peterlaursen
    Participant

    To generate the ALTER TABLE statement you may use the ALTER TABLE gui and copy the statement from HISTORY tab. Once you have one example I think you can easily make variations of it. If ODBC does not return that information we cannot help.

    We will check import of comments from Office 2000 (hopefully we are able to find an old copy!). Maybe this is an issue that can be solved.

Viewing 15 posts - 3,331 through 3,345 (of 7,398 total)