db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3850) Remove unneeded workarounds for DERBY-177 and DERBY-3693
Date Sat, 06 Sep 2008 00:56:44 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628808#action_12628808
] 

Bryan Pendleton commented on DERBY-3850:
----------------------------------------

I see the same results. I built with revision 688273 and removed the commit from predicatesIntoViews.sql,
and the test took 4.5 minutes. Then I updated to the current head of trunk, and left the commit
removed,
and the test completed in just 20 seconds.

I agree that it is now safe to remove that commit. Thanks for tracking this down!

> Remove unneeded workarounds for DERBY-177 and DERBY-3693
> --------------------------------------------------------
>
>                 Key: DERBY-3850
>                 URL: https://issues.apache.org/jira/browse/DERBY-3850
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL, Test
>    Affects Versions: 10.5.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: d3850-predicatesIntoViews.diff, d3850-predicatesIntoViews.stat,
d3850-test.diff, d3850-wait.diff, d3850-wait.stat
>
>
> After the fix for DERBY-177 and DERBY-3693 was committed, these code clean-ups could
be performed:
>   - remove workaround for DERBY-177 in the tests (search for the string "DERBY-177" to
find them)
>   - remove logic to prevent waiting for table locks in SPSDescriptor.updateSYSSTATEMENTS()
since the new mechanism will prevent waiting for all types of locks

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message