svn commit: r433307 - /db/derby/docs/trunk/src/tools/ctoolsimport27052.dita

[jt...@apache.org]

Author: jta
Date: Mon Aug 21 10:46:22 2006
New Revision: 433307

URL: http://svn.apache.org/viewvc?rev=433307&view=rev
Log:
DERBY-1655 (partial): Add documentation for XML functionality to the Tools
and Utilities Guide.

Committed patch derby1655_tools_html.diff by Laura Stewart <sc...@gmail.com>.

Modified:
    db/derby/docs/trunk/src/tools/ctoolsimport27052.dita

Modified: db/derby/docs/trunk/src/tools/ctoolsimport27052.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tools/ctoolsimport27052.dita?rev=433307&r1=433306&r2=433307&view=diff
==============================================================================
--- db/derby/docs/trunk/src/tools/ctoolsimport27052.dita (original)
+++ db/derby/docs/trunk/src/tools/ctoolsimport27052.dita Mon Aug 21 10:46:22 2006
@@ -1,4 +1,7 @@
 <?xml version="1.0" encoding="utf-8"?>
+ 
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "../dtd/concept.dtd">
 <!-- 
 Licensed to the Apache Software Foundation (ASF) under one or more
 contributor license agreements.  See the NOTICE file distributed with
@@ -15,52 +18,60 @@
 See the License for the specific language governing permissions and  
 limitations under the License.
 -->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="ctoolsimport27052">
+<concept id="ctoolsimport27052" xml:lang="en-us">
 <title>Bulk import/export requirements and considerations</title>
 <prolog><metadata>
-<keywords>
-</keywords>
-</metadata>
-</prolog>
+<keywords><indexterm>import<indexterm>requirements</indexterm></indexterm>
+<indexterm>import<indexterm>limitations</indexterm></indexterm></keywords>
+</metadata></prolog>
 <conbody>
-<dl>
-<dlentry><dt>The table must exist.</dt>
-<dd>For you to import data into a table, the table must already exist in <ph conref="toolsconrefs.dita#prod/productshortname"></ph>.
-The table does not have to be empty. If the table is not empty, bulk import
-performs single inserts which results in slower performance.</dd></dlentry>
-<dlentry><dt>Create indexes and primary key, foreign key, and unique constraints
-first.</dt>
+<dl><dlentry>
+<dt>The table must exist</dt>
+<dd>For you to import data into a table, the table must already exist in <ph
+conref="toolsconrefs.dita#prod/productshortname"></ph>. The table does not
+have to be empty. If the table is not empty, bulk import performs single inserts
+which results in slower performance.</dd>
+</dlentry><dlentry>
+<dt>Create indexes and primary key, foreign key, and unique constraints first</dt>
 <dd> To avoid a separate create index step, create indexes and primary keys
 on tables before you import data. However, if your memory and disk spaces
 resources are limited, you can build the indexes and primary keys after importing
-data.</dd></dlentry>
-<dlentry><dt>Data types.</dt>
-<dd>You can import and export only data of the non-binary, <i>built-in</i> data types. <ph conref="toolsconrefs.dita#prod/productshortname"></ph> implicitly converts the strings to the
-data type of the receiving column. If any of the implicit conversions fail,
-the whole import is aborted. For example, "3+7" cannot be converted
-into an integer. An export that encounters a runtime error stops. 
-<note>You cannot import or export the binary data types: BLOB, CLOB, CHAR FOR BIT
-DATA, VARCHAR FOR BIT DATA, or LONG VARCHAR FOR BIT DATA. </note></dd></dlentry>
-<dlentry><dt>Locking during import.</dt>
-<dd>Import procedures use the same isolation level as the connection in
-which they are executed to insert data into tables. During import, the entire
-table is exclusively locked irrespective of the isolation level.</dd></dlentry>
-<dlentry><dt>Locking during export.</dt>
-<dd>Export procedures use the same isolation level as the connection in
-which they are executed to fetch data from tables.</dd></dlentry>
-<dlentry><dt>Import behavior on tables with triggers.</dt>
-<dd>The import procedure fires INSERT triggers when data is appended to
-the table. The REPLACE option is not allowed when triggers are enabled on
-the table.</dd></dlentry>
-<dlentry><dt>Restrictions on the REPLACE option.</dt>
+data.</dd>
+</dlentry><dlentry>
+<dt>Data types</dt>
+<dd>You can import and export only data of the non-binary, <i>built-in</i> data
+types. <ph conref="toolsconrefs.dita#prod/productshortname"></ph> implicitly
+converts the strings to the data type of the receiving column. If any of the
+implicit conversions fail, the whole import is aborted. For example, "3+7"
+cannot be converted into an integer. An export that encounters a runtime error
+stops.  <note>You cannot import or export the binary data types: BLOB, CLOB,
+CHAR FOR BIT DATA, VARCHAR FOR BIT DATA, or LONG VARCHAR FOR BIT DATA. Additionally,
+you cannot import or export the XML data type.</note></dd>
+</dlentry><dlentry>
+<dt>Locking during import</dt>
+<dd>Import procedures use the same isolation level as the connection in which
+they are executed to insert data into tables. During import, the entire table
+is exclusively locked irrespective of the isolation level.</dd>
+</dlentry><dlentry>
+<dt>Locking during export</dt>
+<dd>Export procedures use the same isolation level as the connection in which
+they are executed to fetch data from tables.</dd>
+</dlentry><dlentry>
+<dt>Import behavior on tables with triggers</dt>
+<dd>The import procedure fires INSERT triggers when data is appended to the
+table. The REPLACE option is not allowed when triggers are enabled on the
+table.</dd>
+</dlentry><dlentry>
+<dt>Restrictions on the REPLACE option</dt>
 <dd>If a table that receives imported data already contains data, you can
 either replace or append to the existing data. You can use the REPLACE option
 on tables that have dependent tables, but the replaced data must maintain
 referential integrity, otherwise the import operation will be rolled back.
-You cannot use the REPLACE option if the table has enabled triggers.</dd></dlentry>
-<dlentry><dt>Restrictions on tables.</dt>
-<dd>You cannot use import procedures to import data into a system table
-or a declared temporary table.</dd></dlentry>
-</dl>
-</conbody></concept>
+You cannot use the REPLACE option if the table has enabled triggers.</dd>
+</dlentry><dlentry>
+<dt>Restrictions on tables</dt>
+<dd>You cannot use import procedures to import data into a system table or
+a declared temporary table.</dd>
+</dlentry></dl>
+</conbody>
+</concept>