Devart Forums

The export function doesn't seem to work.

All I receive is this output:
-- Script was generated by Devart dbForge Studio for MySQL, Version 3.10.227.0
-- Script date 4/05/09 10:23:15 PM
-- Server version: 5.1.22-rc-community
-- Client version: 4.1

/*!40014 SET @OLD_FOREIGN_KEY_CHECKS = @@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS = 0 */;

SET NAMES 'utf8';
USE howtopr1_test;

/*!40014 SET FOREIGN_KEY_CHECKS = @OLD_FOREIGN_KEY_CHECKS */;

No data, no table definition.

Is this a bug in the debForge Studio?

Could you please answer some questions:
- Did you have any error messages during export?
- Did you use Schema Export (from the database or connection menu) or Export to SQL (from the table menu) functionality?

Here are snapshots of the steps to export the data:

1) http://tutorialref.com/images/export-my ... orge-1.png

2) http://tutorialref.com/images/schema-ex ... bforge.png

Hope that helps.

Thanks,
vkimura

Thank you for the screenshots, but you didn't answer our question. Please tell us if you received any error messages during export.

I did not receive an error report; however, not exporting data IS the error. Again please note that the following is precisely all I receive:

/*!40014 SET @OLD_FOREIGN_KEY_CHECKS = @@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS = 0 */;

SET NAMES 'utf8';
USE howtopr1_test;

/*!40014 SET FOREIGN_KEY_CHECKS = @OLD_FOREIGN_KEY_CHECKS */;

What good is the export function if all one receives is the above? There is NO table definition AND NO data exported. THIS IS THE ERROR.

Does this make sense?

Thank you,
vkimura

Please do the following:

1. Open the New SQL document
2. Execute the statement "SELECT count(*) FROM " for your table.
3. Do you have some error in the Error List? or Output window. Please, send us this information.
4. Do you see some data in the Data window?

When I type this:
SELECT
*
FROM
`tutorialref_articles`;

I receive this:
1 Table 'howtopr1_test.tutorialref_articles' doesn't exist SQL1.sql 1 1 Devart.DbForge.Utils.Error 1

The database name as it states in the left column is "howtopr1_test.localhost". This could be the cause of the error.

If it is then how does one resolve this error?

In what database the table tutorialref_articles is created?

Please, try to put database name in the SELECT statement as below:
"SELECT
*
FROM
.`tutorialref_articles`"

Then execute this statement in the SQL document and see if any error appeared in the Error List or the Output window. Please, send us this information.
Do you see any data in the Data window?

Here is a snapshot:
http://omusicstudios.com/images/select- ... -table.png

Your table belong to database 'articles', not to 'howtopr1_test' database. So you must write your SELECT statement as below:

SELECT
*
FROM
`articles`.`tutorialref_articles`;

The database 'howtopr1_test' is a default database in your connection. So if you want to select data from tables belong to 'howtopr1_test' you can write their simple names. For tables from other databases you must specify their full names: ..

Hi,

You still did not address the bug that the export feature does not work. Did you forget the original reason for the posting?

Please address this issue.

vkimura

We are trying to find out the reason of the described problem, so we asked you some questions, but unfortunately didn't get your answers. We need to know whether you can execute SELECT statements. If you can't, then Export to SQL feature won't work. To fix the problem, you should set your database connection or security properties.
In addition, could you please describe step-by-step your actions prior to the problem?
Thank you for assistance.

This works:
SELECT
*
FROM
`articles`.`articles_submission`;

The steps are described as previously. Please view the snapshots that was posted earlier.

We have reproduced such a problem on condition that the chosen tables don't have data.

As for Export Data to SQL feature, it exports only table data, but no table definitions. To export a table definition, use the Schema Export (right click on the database/connection node in the Database Explorer and choose "Export & Import -> Schema Export" option from the menu) or Generate DDL (right click on the table node in the Database Explorer).

Anyway, we've added some comments in the result SQL script that explains why it is empty. These improvements are included in dbForge Studio for MySQL v3.50 that will be available in a few days.