[
https://issues.apache.org/jira/browse/DERBY-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-3828.
---------------------------------------
Resolution: Fixed
Derby Info: (was: [Patch Available])
I committed the patch with revision 686238, with the following modifications:
- the original test ran in suites/jdbcapi.runall, which also ran in
derbynetmats. Thus, the test ran both with embedded and network server. I
modified the suite of the new test to also run with both embedded and
networkserver/DerbyNetClient.
- the modification to SURTest_ij.sql to include the protocol in the connect
statement would have made it impossible for the JSR169/J2ME jvms to run,
because the protocol usage causes a call to java.sql.Driver which isn't
available with those jvms.
But, I didn't see anything special about the SURTest database, no properties
being set in the _app.properties file, nor in the .sql itself. So I just
removed the connect statement from the .sql and adjusted the .out file
accordingly.
- I also removed master/DerbyNetClient/SURTest_ij.out and
jdbcapi/SURTest_ij_sed.properties and removed the reference to the old test
from suites/DerbyNet.exclude.
> Convert jdbcapi/SURTest_ij.sql to JUnit.
> ----------------------------------------
>
> Key: DERBY-3828
> URL: https://issues.apache.org/jira/browse/DERBY-3828
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.5.0.0
> Reporter: Erlend Birkenes
> Assignee: Erlend Birkenes
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: Derby-3828_1.diff
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
