[Ritesh]

This is a known bug which will be fixed in SQLyog 3.5

HTH

[Ritesh]

Greetings

The bug will be fixed in SQLyog 3.5 😀

[Ritesh]

SQLyog's Export As Batch Script… option is used by many and we have never faced any problem.

Anyway, try UNCHECKING the option Flush Logs Before Dump and export. Make sure that all the table(s) that you want to Export are listed under Select Table(s) list window.

Are you sure, there is data in the concerned TABLE(s)?

[Ritesh]

Can you attach the SQL script to generate the Table with sample data so that we can reproduce the problem out here and fix it :huh:

[Ritesh]

Please check out the InnoDB manual at InnoDB Homepage for more information on how to setup InnoDB for MySQL

HTH

[Ritesh]

Are you sure that MySQL has been configured for InnoDB Table Handler properly. Please check out the InnoDB manual at InnoDB Homepage for more details.

[Ritesh]

It seems that you are not enclosing the values with ' . To give a valid set of option for ENUM field, provide them in the Length field in the following manner –

'Yes','No' etc

HTH

[Ritesh]

Please read the Technology section of SQLyog FAQ

[Ritesh]

Thank you 😀

[Ritesh]

SQLyog automatically creates column with the correct PRIMARY KEY. Are you getting all columns as NULL?

Please elaborate

[Ritesh]

SQLyog uses C API's to connect to MySQL which is completely different then what is used in ASP connection :huh:

Please check out the MySQL docs on how to connect with ASP/MySQL 😀

[Ritesh]

Cal means the shell tool that comes with MySQL. SQLyog does not add the column name in the Insert Statement to make the resulting file small in size 😀

HTH

[Ritesh]

You cannot do that in the current version of SQLyog.

Thanks for the suggestion 😀

[Ritesh]

You can do that by clicking on the Transform button for the table that you have selected to Import. In the Column Mapping And Transformation Dialog Box that opens us select Delete Rows In the Destination Table… option

HTH

[Ritesh]

Thanks for the information 😀

[Author]

Posts