Page History
...
Here are a few examples using some of these settings.
Automatic table name to file mapping
This example shows how to make the filename the same as the table name in the select statement. The example also shows several select statements. Each will be exported in the SQL format. Since the filename is defined to be automatically set, this means that there will be one file per result set and each file is named by the name of its table.
...
| Note |
|---|
There must be only one table name in a select statement in order to automatically set the filename with the ${dbvis-object}$ variable, i.e if the select joins from several tables or pseudo tables are used, you must explicitly name the file. The ${dbvis-object}$ variable is not substituted with a table name if using the AppendFile="true/clear" parameter. |
Multiple results to a single file
This example shows how all result sets can be exported to a single file. The AppendFile parameter supports the following values.
...
| Code Block |
|---|
@export on; @export set filename="c:\Backups\alltables.sql" appendfile="clear" format="sql"; select * from Orders; select * from Products; select * from Transactions; @export off; |
Using predefined settings
If you save settings when exporting a table or a schema, you can use the Settings parameter to reference the settings file.
| Code Block |
|---|
@export on;
@export set settings="c:\tmp\htmlsettings.xml" filename="c:\Backups\${dbvis-object}$";
select * from Orders;
select * from Products;
select * from Transactions;
@export off; |
Limit the number of exported rows
You can use the @set maxrows command in combination with the @export command to override the Max Rows field value in the SQL Commander tab toolbar.
...
Overview
Content Tools