List:Commits« Previous MessageNext Message »
From:paul Date:January 12 2006 6:19pm
Subject:svn commit - mysqldoc@docsrva: r779 - in trunk: . refman-5.1 refman-common
View as plain text  
Author: paul
Date: 2006-01-12 19:19:12 +0100 (Thu, 12 Jan 2006)
New Revision: 779

Log:
 r6114@frost:  paul | 2006-01-12 12:12:21 -0600
 The ARCHIVE storage engine supports AUTO_INCREMENT now.


Modified:
   trunk/
   trunk/refman-5.1/storage-engines.xml
   trunk/refman-common/news-5.1.xml
   trunk/refman-common/titles.en.ent


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6113
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2101
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6114
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2101

Modified: trunk/refman-5.1/storage-engines.xml
===================================================================
--- trunk/refman-5.1/storage-engines.xml	2006-01-12 18:18:57 UTC (rev 778)
+++ trunk/refman-5.1/storage-engines.xml	2006-01-12 18:19:12 UTC (rev 779)
@@ -3826,6 +3826,19 @@
     </para>
 
     <para>
+      As of MySQL 5.1.6, the <literal>ARCHIVE</literal> engine supports
+      the <literal>AUTO_INCREMENT</literal> column attribute. The
+      <literal>AUTO_INCREMENT</literal> columns can have either a unique
+      or non-unique index. Attempting to create an index on any other
+      column results in an error. The <literal>ARCHIVE</literal> engine
+      also supports the <literal>AUTO_INCREMENT</literal> table option
+      in <literal>CREATE TABLE</literal> and <literal>ALTER
+      TABLE</literal> statements to specify the initial sequence value
+      for a new table or reset the sequence value for an existing table,
+      respectively.
+    </para>
+
+    <para>
       <emphasis role="bold">Storage:</emphasis> Records are compressed
       as they are inserted. The <literal>ARCHIVE</literal> engine uses
       <ulink url="http://www.zlib.net/">zlib</ulink> lossless data

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-01-12 18:18:57 UTC (rev 778)
+++ trunk/refman-common/news-5.1.xml	2006-01-12 18:19:12 UTC (rev 779)
@@ -37,6 +37,45 @@
     for each individual 5.1.x release.
   </para>
 
+  <section id="news-5-1-6">
+
+    <title>&title-news-5-1-6;</title>
+
+    <remark role="note">
+      References to bug numbers should be written after the sentence
+      describing the bugfix, like this: This sentence describes the fix.
+      (Bug #nnnn) It is not necessary to state that the bug was fixed,
+      since "Bugs fixed" already implies this. Use the past tense in
+      describing the bug.
+    </remark>
+
+    <para>
+      Functionality added or changed:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          The <literal>ARCHIVE</literal> storage engine supports the
+          <literal>AUTO_INCREMENT</literal> column attribute and the
+          <literal>AUTO_INCREMENT</literal> table option.
+          <xref linkend="archive-storage-engine"/>.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+    <para>
+      Bugs fixed:
+    </para>
+
+    <remark>
+      ADD AN ITEMIZED LIST WHEN WE HAVE SOME ITEMS THAT GO HERE
+    </remark>
+
+  </section>
+
   <section id="news-5-1-5">
 
     <title>&title-news-5-1-5;</title>

Modified: trunk/refman-common/titles.en.ent
===================================================================
--- trunk/refman-common/titles.en.ent	2006-01-12 18:18:57 UTC (rev 778)
+++ trunk/refman-common/titles.en.ent	2006-01-12 18:19:12 UTC (rev 779)
@@ -1249,6 +1249,7 @@
 <!ENTITY title-news-5-1-3 "Changes in release 5.1.3 (29 November 2005)">
 <!ENTITY title-news-5-1-4 "Changes in release 5.1.4 (21 December 2005)">
 <!ENTITY title-news-5-1-5 "Changes in release 5.1.5 (Not yet released)">
+<!ENTITY title-news-5-1-6 "Changes in release 5.1.6 (Not yet released)">
 <!ENTITY title-news-5-1-x "Changes in release 5.1.x (Development)">
 <!ENTITY title-no-matching-rows "Solving Problems with No Matching Rows">
 <!ENTITY title-nocursor "What Causes <literal>Cursor not found</literal> Errors?">

Thread
svn commit - mysqldoc@docsrva: r779 - in trunk: . refman-5.1 refman-commonpaul12 Jan