db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-268) Add Support for truncate table
Date Tue, 10 May 2005 20:59:04 GMT
     [ http://issues.apache.org/jira/browse/DERBY-268?page=comments#action_64924 ]
     
Satheesh Bandaram commented on DERBY-268:
-----------------------------------------

Truncate table is not part of SQL standard (2003) specification... Mike Matrigali suggested
using import procedure with replace option as a workaround.

"Look at the using the import system procedure with the replace option
set to true and the source import being empty.  I believe this will
run faster than delete, even better would be if your application had
a set of real rows to load when you want to truncate and use the table
again.

Here is a link to 10.0 documentation for the system procedure:
http://incubator.apache.org/derby/manuals/reference/sqlj120.html#HDRIMPORTPROC "


> Add Support for truncate table
> ------------------------------
>
>          Key: DERBY-268
>          URL: http://issues.apache.org/jira/browse/DERBY-268
>      Project: Derby
>         Type: New Feature
>   Components: SQL
>     Reporter: Lance Andersen
>     Priority: Minor

>
> Adding support for truncate table command will aid to portability

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message