1
1
<!--
2
- $Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.66 2001/10/09 18:45:59 petere Exp $
2
+ $Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.67 2001/10/30 20:13:44 tgl Exp $
3
3
-->
4
4
5
5
<chapter id="datatype">
@@ -623,6 +623,10 @@ NUMERIC
623
623
<primary>serial</primary>
624
624
</indexterm>
625
625
626
+ <indexterm zone="datatype-serial">
627
+ <primary>bigserial</primary>
628
+ </indexterm>
629
+
626
630
<indexterm zone="datatype-serial">
627
631
<primary>serial4</primary>
628
632
</indexterm>
@@ -679,14 +683,14 @@ CREATE TABLE <replaceable class="parameter">tablename</replaceable> (
679
683
<para>
680
684
The type names <type>serial</type> and <type>serial4</type> are
681
685
equivalent: both create <type>integer</type> columns. The type
682
- names <type>bigserial</type> and <type>serial8</type> works just
683
- the same way, except that it creates a <type>bigint</type>
684
- column. <type>serial8 </type> should be used if you anticipate
686
+ names <type>bigserial</type> and <type>serial8</type> work just
687
+ the same way, except that they create a <type>bigint</type>
688
+ column. <type>bigserial </type> should be used if you anticipate
685
689
use of more than 2^31 identifiers over the lifetime of the table.
686
690
</para>
687
691
688
692
<para>
689
- Implicit sequences supporting the <type>serial</type> are
693
+ Implicit sequences supporting the <type>serial</type> types are
690
694
not automatically dropped when a table containing a serial type
691
695
is dropped. So, the following commands executed in order will likely fail:
692
696
@@ -697,7 +701,8 @@ CREATE TABLE <replaceable class="parameter">tablename</replaceable> (<replaceabl
697
701
</programlisting>
698
702
699
703
The sequence will remain in the database until explicitly dropped using
700
- <command>DROP SEQUENCE</command>.
704
+ <command>DROP SEQUENCE</command>. (This annoyance will probably be
705
+ changed in some future release.)
701
706
</para>
702
707
</sect2>
703
708
</sect1>
0 commit comments