Feature: Show Errors in History Tab

[yonder]

Hello again,

it would be great if the error messages that are shown in the

messages tab would be merged into the history view (or other way round).

It is very difficult to find errors in a large sql dump, because it is not possible

to see the statement that caused the error.

Bye,

Yonder.

PS: Rather-Mysql-specific: Has anyone experienced problems when importing really large

batch insert statements? We tried to import a dump that contained a single

insert statement with about 1 Megabyte of data and the result was that

about half of the data was imported correctly and the other half got

thrown into the last successful row inserted into a text field, so that

this field contained the statements as text 🙁

(Experienced with MySQL 4.0.23)

[peterlaursen]

concerning: importing really large batch insert statements: There is a setting in the MySQL server configuration file (my.cnf/my.ini) name MAX-ALLOWED_PACKET that controls this. If the server configuration is under your control you can raise the value (and stop and restart mySQL for the changes to take effect). Actually there migth be two MAX-ALLOWED_PACKET -values: one for use with the Mysqldump -utility another for clients like SQLyog.

If the .sql file is generated with SQLyog you can have one row with each INSERT statement by unchecking “create bulk insert statements” in the export dialogue.

[Ritesh]

@yonder – Thanks.

I have forwarded your issue to my development team.

[yonder]

Thanks Peter for the parameter… I should have looked at the error message more thoroughly 😉

@Ritesh: Thanks a lot. Hope it will be implemented 😀

[Author]

Posts