[
https://issues.apache.org/jira/browse/DERBY-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-5368:
--------------------------------------
Attachment: DERBY-5368-2.diff
DERBY-5368-2.stat
attaching a patch which splits off the multiconnect test case out of ij2.sql
into a separate section, ij2b.sql, with matching .out file and a section in
ij2Test.java which runs that only with vms that support jdbc 3 (and higher).
This does also add the ij.database property testing back in, which causes an
extra connection at start, which then gives the same result for the main
section of the test for JSR169/J2ME and the other jvms. Also causes the multi
connect test case to be a little different; i.e. it now has an extra connection
(and connects to an existing database). I think this is ok, but will wait for a
couple of days for comments before checking this in.
> Convert tools/ij2.sql to junit
> ------------------------------
>
> Key: DERBY-5368
> URL: https://issues.apache.org/jira/browse/DERBY-5368
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Houx Zhang
> Assignee: Houx Zhang
> Labels: gsoc2011
> Fix For: 10.9.0.0
>
> Attachments: 5368-1.patch, 5368-1.stat, DERBY-5368-2.diff,
> DERBY-5368-2.stat
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
