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: Error Code: 1005 #17578
    mattyb
    Member

    I unchecked “create bulk insert statements”, redid the dump and then imported – worked. Table names have been changed to lower case but what should I expect on a Windows machine. The import did take a while though : 5M file and about 30 mins (the file was already on the PC running Windows XP and MySQL).

    I'll edit the my.ini for the packet sizes.

    Thanks for your help Peter.

    Matt

    in reply to: Error Code: 1005 #17575
    mattyb
    Member

    Peter,

    Yes logged on as the root user for MySQL on both machines.

    Yes, SQLyog and the MySQL server are both running on my PC – Windows XP Pro

    When trying to inject the raw sql file I get :

    C:>mysql -u root -p < V010MT01_SQLyog2.sql Enter password: ******** ERROR 1153 (08S01) at line 209: Got a packet bigger than 'max_allowed_packet' bytes I launched the mysql client and injected the V010MT01_SQLyog2.sql file I got some errors : ERROR 1153 (08S01) at line 209: Got a packet bigger than 'max_allowed_packet' bytes ERROR 2006 (HY000): MySQL server has gone away No connection. Trying to reconnect… Connection id: 13 Current database: reel_db … ERROR 1217 (23000): Cannot delete or update a parent row: a foreign key constraint fails ERROR 1050 (42S01): Table 'libelle_civilite' already exists Query OK, 0 rows affected (0.00 sec) … ERROR 1062 (23000): Duplicate entry '1' for key 1 – saw this one twice ERROR 1050 (42S01): Table 'offre' already exists – for three different tables ERROR 1216 (23000): Cannot add or update a child row: a foreign key constraint fails The base and tables 'seem' fine though after examining them for 2 minutes ;-). Charset is latin1 for both SQL dump scripts. The 'raw' mysqldump script has : /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; The SQLyog generated script doesn't mention collation anywhere. Under Server variables for the Windows XP machine I have for character_set : client, connection, database, results and server as latin1. Under character_set_system I have utf8 Under the RHEL machine its the same. Both are brand new installs – no upgrade. The RHEL had a compiled install, the Windows machine used the mysql-4.1.9-win32.zip from the MySQL website. The reason that I put 4.1.9 on the XP machine was that I wanted to use the same version as on RHEL. If I upgrade on the XP box, my tests won't really be valid. I have the feeling that this is an SQLyog thing. The 'raw' mysqldump script has settings for collation, unique checks while the SQLyog script doesn't. We're not going to use SQLyog in production, but it would have been nice to be able to export/import through SQLyog. Oh well, I'll have to learn to use MySQL Administrator to export/import. Thanks for your help and advice, if there are any more questions I'll try and answer them. Matt P.S. Just looked at the lower_case_table_names parameter on both machines : they're different, the XP machine has a value of 1 and the RHEL machine has 0.

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