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

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: Sql Dump Fails To Restore #29466
    Brian H.
    Member

    I did a little more testing and discovered that if I do a mysqldump to include the views (and everything else in the D:cool:, the dumpfile is created without errors. If I take that dump file and import it into a NEWly created database with mysql command line tools, it imports correctly, with no errors.

    When I then go into SQLyog and try to export the VIEWS from the newly created database, I get the same error as before. Below are the commands I used to test in mysql:

    # mysqldump -uuser -p –skip-opt –all –complete-insert mrm>mrmfulltest.sql

    (in mysql) CREATE DATABASE exporttest;

    # mysql -uuser -p exporttest

    in reply to: Exporting Database – Error 1118 #29463
    Brian H.
    Member

    Thanks Peter for the quick response!

    I have done more testing and discovered that this is actually a VIEW that his causing the error, not a “table.” But I'm not the developer, only an admin, so I'm not sure how to get the CREATE statement at this point until I talk to the developers and DBA. I assume that when I do a mysqldump that I am not actually dumping the VIEWs, and that is why I'm not getting the error. I'm not sure why an error isn't being thrown during the running of the application, but I will investigate further.

    We are using MySQL version 5.1.35-community directly from MySQL.

    peterlaursen wrote on Aug 14 2009, 12:35 PM:
    It is a restriction with InnoDB. Refer to: http://dev.mysql.com/doc/refman/5.0/en/inn…strictions.html

    #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”

    .. but I can't explain why mysqldump does not suffer from this. Also not why it happens during export. We will need to study it.

    Please tell:

    1) the MySQL version

    2) Can you paste the CREATE STATEMENT for the table (create a ticket for privacy if you wnat)

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