db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Weiner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DDLUTILS-90) writeSchemaSqlToFile task produces empty output file
Date Thu, 13 Apr 2006 18:22:00 GMT
    [ http://issues.apache.org/jira/browse/DDLUTILS-90?page=comments#action_12374390 ] 

Ken Weiner commented on DDLUTILS-90:

I don't think I had a problem accessing the database because if I changed my schema file,
I could see the results reflected in the database.  I also didn't see any error messages that
indicated that there was an error.  The database I was using was HSQLDB.  Is it possible that
HSQLDB does not support something that the alterDatabase function is trying to do, but is
not reporting an error?

> writeSchemaSqlToFile task produces empty output file
> ----------------------------------------------------
>          Key: DDLUTILS-90
>          URL: http://issues.apache.org/jira/browse/DDLUTILS-90
>      Project: DdlUtils
>         Type: Bug

>   Components: Ant Tasks
>     Reporter: Ken Weiner
>     Assignee: Thomas Dudziak

> Running
> <writeSchemaSqlToFile outputFile="schema.sql"/>
> results in an empty schema.sql file, but setting the alterDatabase attribute to false
results in a properly written schema.sql file like so:
> <writeSchemaSqlToFile alterDatabase="false" outputFile="schema.sql"/>
> I am guessing that the sql should be written to the file, no matter what the value of
the alterDatabase attribute.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message