[
https://issues.apache.org/jira/browse/DERBY-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534464#comment-13534464
]
Ari Maniatis commented on DERBY-1851:
-------------------------------------
Some notes for people finding this issue:
The dblook tool (http://db.apache.org/derby/docs/10.8/tools/ctoolsdblook.html)
will get the structure of the database and export it as a SQL script.
But it doesn't extract the data.
You could perhaps use the backup and restore utilities, but the format of a
Derby backup is not a sql script.
The Apache 'ddlutils' tool can extract and move the data, I believe. See:
http://db.apache.org/derby/integrate/db_ddlutils.html and
http://db.apache.org/ddlutils/
(This was copied from
http://stackoverflow.com/questions/9275712/derby-database-to-sql-script)
> Create full SQL export of Database (including INSERTs)
> ------------------------------------------------------
>
> Key: DERBY-1851
> URL: https://issues.apache.org/jira/browse/DERBY-1851
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 10.1.3.1
> Reporter: Alexander Schatten
> Priority: Minor
>
> Currently DERBY supports to backup a database (binary) or to create the DDL
> of the database. It would be very helpful (as known from hsqldb) if it would
> be possible to export a full database including content; i.e., CREATE, ALTER
> and INSERT statements.
> This is particularly nice for development issues when a schema is often
> changing...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
