You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2013/06/20 06:48:23 UTC
[jira] [Commented] (DERBY-6102) dblook.log is always created in
current working dir, no matter what
[ https://issues.apache.org/jira/browse/DERBY-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688863#comment-13688863 ]
Dag H. Wanvik commented on DERBY-6102:
--------------------------------------
The dbloog.log file is intended for errors/warnings. The output file, specified with the "-o" option contains the generated SQL (std out if not given). Closing as not an issue.
> dblook.log is always created in current working dir, no matter what
> -------------------------------------------------------------------
>
> Key: DERBY-6102
> URL: https://issues.apache.org/jira/browse/DERBY-6102
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.9.1.0
> Reporter: Mark
>
> new dblook(new String[]{"-d", "jdbc:derby:memory:unit-testing;", "-verbose"});
> creates an empty dblook.log in the current directory.
> new dblook(new String[]{"-d", "jdbc:derby:memory:unit-testing;", "-verbose", "-o", "/tmp/some.log"});
> creates an empty dblook.log in the current directory in addition to /tmp/some.log.
--
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