|
12 | 12 | alink="#0000FF"> |
13 | 13 | <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> |
14 | 14 |
|
15 | | -<P>Last updated:Fri Oct12 23:53:35 EDT 2001</P> |
| 15 | +<P>Last updated:Sat Oct13 01:26:55 EDT 2001</P> |
16 | 16 |
|
17 | 17 | <P>Current maintainer: Bruce Momjian (<Ahref= |
18 | 18 | "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR> |
@@ -1003,11 +1003,13 @@ <H4><A name="4.15">4.15</A>) What is the difference between the |
1003 | 1003 | stored out-of-line by<SMALL>TOAST</SMALL>, so the space on disk |
1004 | 1004 | might also be less than expected.</P> |
1005 | 1005 |
|
1006 | | -<P>CHAR() is best when storing strings that are usually the |
1007 | | - same length. VARCHAR() is best when storing variable-length strings, |
1008 | | - but you want to limit how long a string can be. TEXT is for strings |
1009 | | - of unlimited length, maximum 1 gigabyte. BYTEA is for storing |
1010 | | - binary data, particularly values that include NULL bytes.</P> |
| 1006 | +<P><SMALL>CHAR()</SMALL> is best when storing strings that are |
| 1007 | + usually the same length.<SMALL>VARCHAR()</SMALL> is best when |
| 1008 | + storing variable-length strings but it limits how long a |
| 1009 | + string can be.<SMALL>TEXT</SMALL> is for strings of unlimited |
| 1010 | + length, maximum 1 gigabyte.<SMALL>BYTEA</SMALL> is for storing |
| 1011 | + binary data, particularly values that include<SMALL>NULL</SMALL> |
| 1012 | + bytes.</P> |
1011 | 1013 |
|
1012 | 1014 | <H4><Aname="4.16.1">4.16.1</A>) How do I create a |
1013 | 1015 | serial/auto-incrementing field?</H4> |
|