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

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: #27841
    krypta
    Member

    It seems to be working but I think I found another problem.

    1) create a new stored procedure, name it 'test' (no need to put the underscore character in the name)

    2) verify in the query editor if it works with intellisense (it should be there)

    3) right click the stored procedure and select 'Alter stored procedure' and change its name to 'test2' using the suggested code

    [codebox]DELIMITER $$

    DROP PROCEDURE IF EXISTS `mydatabase`.`test`$$

    CREATE DEFINER=`root`@`localhost` PROCEDURE `test2`()

    BEGIN

    SELECT * FROM mytable;

    END$$

    DELIMITER ;[/codebox]

    4) try to look for the new stored procedure in the query editor

    I can't find it in my intellisense even if I refresh the object browser.

    Please, let me know if this works for you.

    Thanks in advance.

    Giovanni Acerbi.

    in reply to: #27547
    krypta
    Member

    Thank you for your quick reply.

    You are right! I got the same error trying the same operation using the command line, so I tried to look for error 1118 on the MySql site and found this:

    Although InnoDB supports row sizes larger than 65535 internally, you cannot define a row containing VARBINARY or VARCHAR columns with a combined size larger than 65535:

    mysql> CREATE TABLE t (a VARCHAR(8000), b VARCHAR(10000),

    -> c VARCHAR(10000), d VARCHAR(10000), e VARCHAR(10000),

    -> f VARCHAR(10000), g VARCHAR(10000)) ENGINE=InnoDB;

    ERROR 1118 (42000): Row size too large. The maximum row size for the

    used table type, not counting BLOBs, is 65535. You have to change some

    columns to TEXT or BLOBs

    Anyway thanks again for your help.

    Giovanni Acerbi.

    in reply to: Strange structure synchronization #16700
    krypta
    Member

    It seems to be ok now.

    Thank you very much.

    Krypta.

    in reply to: Strange structure synchronization #16697
    krypta
    Member

    This is the sql script created by sqlyog for the left side:

    /* Alter table in Second database */ <- right alter table `galassia`.`tblsoci`, type=MyISAM; <- wrong and this is the one for the right side: /* Alter table in First database */ <- right alter table `galassia`.`tblsoci`, type=InnoDB; <- wrong The scripts should be: /* Alter table in Second database */ alter table `galassia`.`tblsoci`, type=InnoDB; /* Alter table in First database */ alter table `galassia`.`tblsoci`, type=MyISAM; The trouble seems to be that only the table type is to be modified. I tried to change a property of a column in the same table and the script was right. Hope this helps. Regards. Krypta.

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