Bug In Export As Sql Statements

[weavelink]

Hi,

First of all congratulations on your great product.

We're using the sqlyog community version 5.2 BETA.

When we do an export of our data in sql statements, then the last record is never exported. This happens in Bulk insert mode as well in non Bulk insert mode.

Best regards,

Weavelink

[peterlaursen]

I cannot reproduce!

Please attach a screenshot of the settings dialogue and a small table to reproduce with! Preferably not bigger than it is possible to 'have it in my head'.

What is 'the last' record? The order may depend or what KEYs are in the table and need neot be the same as it is displayed. Please try SELECT COUNT(*), export, import to a test database and repeat SELECT COUNT(*)

[weavelink]

Hello Peter,

Thanks for the fast reply.

I have exported a small table, containing only 2 records and only 1 record is dumped in the SQL file.

I'm using MySQL 5.0.22, and SQLyog Community edition 5.2 beta 1.

I have attached the following files / screenshots to this post:

Quote:

preferences_dialog.jpg => Screenshot SQLyog preferences.

table_properties.jpg => Properties of the table that is exported.

data_before_export.jpg => The data in the table before the export.

count_before_export.jpg => Number of records in the table before export.

export_dialog.jpg => Screenshot of the export dialog.

test.sql => SQL file that was generated by the export.

data_after_import.jpg => The data in the table after import.

count_after_import.jpg => Number of records in the table after import.

I hope that this can help you.

Thanks and best regards,

Weavelink

[weavelink]

Hello Peter,

Sorry my previos reply was sent too soon, without all the attachments.

Thanks for the fast reply.

I have tested the export with a small table, containing only 2 records, of which only 1 is dumped during the export.

I'm using MySQL version 5.0.22 and SQLyog community edition v5.2 beta 1.

I have attached the following files / screenshots to this post :

Quote:

preferences_dialog.jpg => SQLyog preferences

table_properties.jpg => Properties of the table that will be exported

count_before_export.jpg => Number of records in the table before export

data_before_export.jpg => Data in the table before export

export_dialog.jpg => Screenshot of the export dialog

test.sql.txt => The SQL file that was generated by the export

count_after_import.jpg => Number of records in the table after import

data_after_import.jpg => Data in the table after import

Thanks and best regards,

Wim

Hello Peter,

Thanks for the fast reply.

I have tested the export with a small table, containing only 2 records, of which only 1 is dumped during the export.

I'm using MySQL version 5.0.22 and SQLyog community edition v5.2 beta 1.

I have attached the following files / screenshots to this post :

Quote:

preferences_dialog.jpg => SQLyog preferences

table_properties.jpg => Properties of the table that will be exported

count_before_export.jpg => Number of records in the table before export

data_before_export.jpg => Data in the table before export

export_dialog.jpg => Screenshot of the export dialog

test.sql => The SQL file that was generated by the export

count_after_import.jpg => Number of records in the table after import

data_after_import.jpg => Data in the table after import

Thanks and best regards,

Wim

[peterlaursen]

Not reproducable here.

I import your SQL, add a row manually, export, edit the file (change the tablename) and it imports like atached picture.

Please try to check the 'CREATE BULK INSERT' box in teh export dialogue. And set the BULK value very high in preferences. Every row of data will now be int the same INSERT statement. Now what happens?

is EVERYTHING inserted, or are NO DATA inserted?

Please let me see the SQL BEFORE the import. Are all data in there?

Next ensure that 'log batch jobs' is enabled in 'preferences'.

Check HISTORY after the import.

If server 'general log' is enabled compare the server log.

It very much look like (refer to the other discusssion) with your server/network setup that the last line is cached or dropped somewhere and never reaches the server!

[peterlaursen]

One more idea.

Try to add a 'silly' statement at the end of the file.

something like “SET @silly = 'this is the last statement';” for instance.

You could even add

SET @silly = 'this is the last statement';

SELECT @silly into outfile 'c:\silly.text';

does the file 'silly.txt' exist in C: after that?

[peterlaursen]

I have been informed that there was an issue with 5.2 beta1 tht it would sometimes not export the last row.

I did refer to this thread that I thought was yours too:

http://www.webyog.com/forums//index.php?showtopic=2343

Was I mistaken in that assumption?

[weavelink]

Hello Peter,

I have just downloaded and installed version 5.2 beta 2 and it seems like the problem is fixed in this version.

Thanks for your help !

Best regards,

Wim

[Author]

Posts