Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 98040 invoked from network); 21 Sep 2010 19:54:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 Sep 2010 19:54:57 -0000 Received: (qmail 46843 invoked by uid 500); 21 Sep 2010 19:54:57 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 46797 invoked by uid 500); 21 Sep 2010 19:54:56 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 46790 invoked by uid 99); 21 Sep 2010 19:54:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Sep 2010 19:54:56 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Sep 2010 19:54:56 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o8LJsZDZ022384 for ; Tue, 21 Sep 2010 19:54:35 GMT Message-ID: <4108373.326061285098875714.JavaMail.jira@thor> Date: Tue, 21 Sep 2010 15:54:35 -0400 (EDT) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-268) Add Support for truncate table In-Reply-To: <699266124.1115755469806.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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.