[
https://issues.apache.org/jira/browse/DERBY-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481404
]
Manjula Kutty commented on DERBY-2392:
--------------------------------------
Thanks for looking in to this patch and committing
- Yes I didn't put the if (verbose) {}, for prints in the catch blocks
intentionally. So that in any mode it should print the exceptions caught.
>>In the main method, in the for loop where you parse the arguments, if an
>>unknown argument is passed, you return from the main method. It might be a
>>good idea to System.exit(1) here. Not sure how this might interact with a
>>possible Junit wrapper for the test, though.
-- Me too don't have any idea about this. Will look more to it while creating
the junit wrapper calss for this test
> Create verbose option to get the queries which are currently running
> --------------------------------------------------------------------
>
> Key: DERBY-2392
> URL: https://issues.apache.org/jira/browse/DERBY-2392
> Project: Derby
> Issue Type: Sub-task
> Reporter: Manjula Kutty
> Assigned To: Manjula Kutty
> Priority: Trivial
> Attachments: DERBY-2392_diff_ver1.txt, DERBY-2392_diff_ver2.txt,
> DERBY-2392_stat_ver1.txt, DERBY-2392_stat_ver2.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
