[
https://issues.apache.org/jira/browse/DERBY-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Houx Zhang updated DERBY-5342:
------------------------------
Attachment: 5342-1.patch
Hi, Bryan.
This project doesn't related to DERBY-5332, as in ij3_app.properties, it says:
# ij3 wants to test an alternate path for driver loading
# from URL setting along
ij.database=jdbc:derby:wombat;create=true
so I think it's better to make a new subclass of ScriptTestCase than to add it
in ToolScripts.
In fact, this project relates to "DERBY-5327", in ij5_app.properties, it says:
ij.showNoConnectionsAtStart=false
ij.showNoCountForSelect=false
however, ScriptTestCase doesn't support this two properties. With the two
properties supporting, ij5.sql is fit to add into ToolScripts.
I have changed utilMain in 5342-1.patch to support the two properties, and
tested it well, however, I haven't yet to change the test cases affected by
it.
I'm not sure weather you think this project is not neccessary, so I will have a
break first and get your advice. Thanks!
> make ScriptTestCase support "ij.showNoCountForSelect" and
> "ij.showNoConnectionsAtStart"
> ---------------------------------------------------------------------------------------
>
> Key: DERBY-5342
> URL: https://issues.apache.org/jira/browse/DERBY-5342
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Houx Zhang
> Assignee: Houx Zhang
> Labels: gsoc2011
> Attachments: 5342-1.patch
>
>
> Now, ScriptTestCase doesn't support property "ij.showNoConnectionsAtStart"
> (do nothing for it) and "ij.showNoCountForSelect"(it always works as
> "ij.showNoCountForSelect" = "flase").
> It will be better if the two properties be supported. To realise this,
> utilMain.goScript(Connection conn, LocalizedInput in) should be changed.
> Besides, some subclasses of ScripTestCase will be adapted accordingly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
