db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-4801) Re-use the bulk-import mechanism to support the TRUNCATE command
Date Fri, 28 Sep 2012 18:29:07 GMT

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

Mamta A. Satoor updated DERBY-4801:
-----------------------------------

    Urgency: Normal
     Labels: derby_triage10_10  (was: )
    
> Re-use the bulk-import mechanism to support the TRUNCATE command
> ----------------------------------------------------------------
>
>                 Key: DERBY-4801
>                 URL: https://issues.apache.org/jira/browse/DERBY-4801
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_10
>
> Re-using the bulk-import code to support TRUNCATE will increase our confidence in TRUNCATE.
In addition, the bulk-import code will allow TRUNCATE to succeed in the following edge case,
which currently raises an exception:
> o The truncated table is referenced by a foreign key
> o But there are no rows in the referencing table
> See the discussion on the related DERBY-268 issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message