[
https://issues.apache.org/jira/browse/DERBY-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junjie Peng updated DERBY-3699:
-------------------------------
Attachment: holdCursorJDBC30_tmp.java
There are still some other improvements about SQLToJUnit.
When convert
org.apache.derbyTesting.functionTests.master.DerbyNet.holdCursorJDBC30.out to
junit with SQLToJunit, there are some places SQLToJunit can not convert, which
can be summarized into 5 items:
1. [**:: UNCONVERTED ::**] IJ ERROR: Unable to establish cursor.
2. [**:: UNCONVERTED ::**] get with hold cursor test1 as 'select * from
foo for update'
3. test1.next();
[**:: UNCONVERTED ::**] No current row
test1.close();
4. [**:: UNCONVERTED ::**] exit
5. test1.next();
[**:: UNCONVERTED ::**] 1
-----------
6
It seems, 1 - 3 should be resolved first. 5 is the same question with 3.
> SQLToJUnit improvements
> -----------------------
>
> Key: DERBY-3699
> URL: https://issues.apache.org/jira/browse/DERBY-3699
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Priority: Minor
> Attachments: holdCursorJDBC30_tmp.java
>
>
> In converting predicatePushdown.sql there were a few potential
> improvements/bugs that came up in the SQLToJUnit tool.
> -- Does not preserve formatting of multi line sql statements making sql
> harder to read.
> -- Does not insert line breaks after single line comments causing problems
> with optimizer directives.
> - Chokes on Runtime Statistics. We can't automate the parsing but perhaps
> calls to runtime statistics can be replaced with calls to
> SQLUtilities.getRuntimeStatisticsParser(st);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
