db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-3699) SQLToJUnit improvements
Date Thu, 20 Jun 2013 22:51:20 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren updated DERBY-3699:
--------------------------------------

    Urgency: Low
    
> 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.1.1
>            Reporter: Kathey Marsden
>            Priority: Minor
>              Labels: derby_triage10_11
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message