db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1014) Make tests less sensitive to pre-fetching
Date Wed, 22 Feb 2006 14:51:38 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1014?page=all ]

Knut Anders Hatlen updated DERBY-1014:
--------------------------------------

    Other Info: [Patch available]

> Make tests less sensitive to pre-fetching
> -----------------------------------------
>
>          Key: DERBY-1014
>          URL: http://issues.apache.org/jira/browse/DERBY-1014
>      Project: Derby
>         Type: Sub-task
>   Components: Test
>     Reporter: Knut Anders Hatlen
>     Assignee: Knut Anders Hatlen
>     Priority: Minor
>  Attachments: DERBY-1014-v1.diff, DERBY-1014-v1.stat
>
> Some tests are very sensitive to changes in pre-fetching, either
> because they call SYSCS_UTIL.SYSCS_GET_RUNTIMESTATISTICS() which
> displays the number of rows seen, or because a failure that normally
> is exposed when calling ResultSet.next() is exposed when calling
> Statement.execute().
> Most of these tests are not testing when or how much data is
> pre-fetched. If we make the tests less sensitive to pre-fetching, it
> is easier to catch the real regressions when changing the way Derby is
> pre-fetching data. Also, patches in that area of the code will be
> smaller (fewer test changes) and easier to review.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message