db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-268) Add Support for truncate table
Date Tue, 28 Sep 2010 13:56:33 GMT

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

Rick Hillegas updated DERBY-268:

    Attachment: derby-268-03-aa-npe.diff

Attaching derby-268-03-aa-npe.diff. This patch fixes the NPE seen in the TruncatorConcurrency
experiments when the re-initialization statement is TRUNCATE TABLE or DROP TABLE. I am running
regression tests now.

Touches the following files:


M      java/engine/org/apache/derby/impl/store/access/conglomerate/GenericController.java

The NPE occurred while trying to update the statistics for a conglomerate which has been dropped.
The fix is to not update the statistics if the conglomerate no longer exists.


M      java/testing/org/apache/derbyTesting/functionTests/tests/lang/TruncateTableTest.java

Added a test case to track this fix.

> Add Support for truncate table
> ------------------------------
>                 Key: DERBY-268
>                 URL: https://issues.apache.org/jira/browse/DERBY-268
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Lance Andersen
>            Assignee: Eranda Sooriyabandara
>            Priority: Minor
>         Attachments: derby-268-01-ab-enableForInsaneBuilds.diff, derby-268-02-aa-permsTest.diff,
derby-268-03-aa-npe.diff, Derby-268.diff, tests.diff, TruncateConcurrency.java, TruncateConcurrency.java,
> Adding support for truncate table command will aid to portability

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

View raw message