Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <32825052.277381284844292719.JavaMail.jira@thor>
Date: Sat, 18 Sep 2010 17:11:32 -0400 (EDT)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4802) Document the TRUNCATE command
In-Reply-To: <21512149.230471284651992580.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bryan Pendleton updated DERBY-4802:
-----------------------------------

    Attachment: rrefsqljtruncatetable.html

Adding ANT_OPTS=-x512m to my docs build seems to work
around the out-of-memory problem I was experiencing.

Attached is an initial version of a TRUNCATE TABLE reference page,
formatted as HTML.

Are there specific details about TRUNCATE TABLE that we
want to make sure that we mention on the docs page?


> Document the TRUNCATE command
> -----------------------------
>
>                 Key: DERBY-4802
>                 URL: https://issues.apache.org/jira/browse/DERBY-4802
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Rick Hillegas
>            Assignee: Bryan Pendleton
>         Attachments: docs.diff, rrefsqljtruncatetable.html
>
>
> As part of DERBY-268, we should document the TRUNCATE command. This involves adding a small section to the Reference Guide.

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