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] Commented: (DERBY-268) Add Support for truncate table
Date Tue, 21 Sep 2010 19:54:35 GMT

    [ https://issues.apache.org/jira/browse/DERBY-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913209#action_12913209

Rick Hillegas commented on DERBY-268:

Hi Dag,

We don't have a functional spec for this feature beyond our sense about what it means to subset
the brief SQL 2008 language. The concurrency issues you raise are worth probing with some
tests. There could be some bugs here. At a high level, TRUNCATE TABLE is implemented as a
DDL operation (more specifically as a kind of ALTER TABLE statement). That means that like
other DDL, an attempt is made to invalidate other statements which reference the table in
question. That would be the point at which those other statements would be able to object
that an in-flight cursor blocks the DDL. Thanks.

> 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.diff, tests.diff
> 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