Mention SQL9x precision syntax for date/time types.
Use PostgreSQL consistantly throughout docs. Before, usage was split evenly
between Postgres and PostgreSQL.
#
#
# IDENTIFICATION
-# $Header: /cvsroot/pgsql/doc/src/sgml/Makefile,v 1.45 2001/11/18 20:35:02 petere Exp $
+# $Header: /cvsroot/pgsql/doc/src/sgml/Makefile,v 1.46 2001/12/08 03:24:21 thomas Exp $
#
#----------------------------------------------------------------------------
postgres.html: catalogs.gif connections.gif
-COLLATEINDEX = $(PERL) $(DOCBOOKSTYLE)/bin/collateindex.pl -f -g -t 'Index'
+#COLLATEINDEX = $(PERL) $(DOCBOOKSTYLE)/bin/collateindex.pl -f -g -t 'Index'
+COLLATEINDEX = $(PERL) /usr/bin/collateindex.pl -f -g -t 'Index'
ifeq (,$(wildcard HTML.index))
bookindex.sgml:
+ifeq (,$(wildcard $(COLLATEINDEX)))
+ touch $@
+else
$(COLLATEINDEX) -o $@ -N
+endif
+
setindex.sgml:
+ifeq (,$(wildcard $(COLLATEINDEX)))
+ touch $@
+else
$(COLLATEINDEX) -x -o $@ -N
+endif
else
bookindex.sgml: HTML.index
$(COLLATEINDEX) -i 'bookindex' -o $@ $<
+
setindex.sgml: HTML.index
$(COLLATEINDEX) -i 'setindex' -x -o $@ $<
endif
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/cvs.sgml,v 1.20 2001/11/21 05:53:40 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/cvs.sgml,v 1.21 2001/12/08 03:24:22 thomas Exp $
CVS code repository
Thomas Lockhart
-->
# at the date specified below
#*default date=97.08.29.00.00.00
-# base directory points to where CVSup will store its 'bookmarks' file(s)
+# base directory where CVSup will store its 'bookmarks' file(s)
# will create subdirectory sup/
#*default base=/opt/postgres # /usr/local/pgsql
*default base=/home/cvs
-# prefix directory points to where CVSup will store the actual distribution(s)
+# prefix directory where CVSup will store the actual distribution(s)
*default prefix=/home/cvs
# complete distribution, including all below
*default delete use-rel-suffix
*default tag=.
-# base directory points to where CVSup will store its 'bookmarks' file(s)
+# base directory where CVSup will store its 'bookmarks' file(s)
*default base=<replaceable class="parameter">/usr/local/pgsql</replaceable>
-# prefix directory points to where CVSup will store the actual distribution(s)
+# prefix directory where CVSup will store the actual distribution(s)
*default prefix=<replaceable class="parameter">/usr/local/pgsql</replaceable>
# complete distribution, including all below
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.77 2001/11/28 20:49:09 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.78 2001/12/08 03:24:22 thomas Exp $
-->
<chapter id="datatype">
</row>
<row>
- <entry><type>time [ without time zone ]</type></entry>
+ <entry><type>time [ (<replaceable>p</replaceable>) ] [ without time zone ]</type></entry>
<entry></entry>
<entry>time of day</entry>
</row>
<row>
- <entry><type>time with time zone</type></entry>
+ <entry><type>time [ (<replaceable>p</replaceable>) ] with time zone</type></entry>
<entry><type>timetz</type></entry>
<entry>time of day, including time zone</entry>
</row>
<row>
- <entry><type>timestamp without time zone</type></entry>
+ <entry><type>timestamp [ (<replaceable>p</replaceable>) ] without time zone</type></entry>
<entry><type>timestamp</type></entry>
<entry>date and time</entry>
</row>
<row>
- <entry><type>timestamp [ with time zone ]</type></entry>
+ <entry><type>timestamp [ (<replaceable>p</replaceable>) ] [ with time zone ]</type></entry>
<entry><type>timestamptz</type></entry>
<entry>date and time, including time zone</entry>
</row>
</thead>
<tbody>
<row>
- <entry><type>timestamp without time zone</type></entry>
+ <entry><type>timestamp [ (<replaceable>p</replaceable>) ] without time zone</type></entry>
<entry>both date and time</entry>
<entry>8 bytes</entry>
<entry>4713 BC</entry>
<entry>1 microsecond / 14 digits</entry>
</row>
<row>
- <entry><type>timestamp [ with time zone ]</type></entry>
+ <entry><type>timestamp [ (<replaceable>p</replaceable>) ] [ with time zone ]</type></entry>
<entry>both date and time</entry>
<entry>8 bytes</entry>
<entry>4713 BC</entry>
</tbody>
</tgroup>
</table>
+ </para>
- <note>
- <para>
- Time zones, and time-zone conventions, are influenced by
- political conventions, not just physical effects. Time zones have
- become somewhat standardized during the 1900's, but continue to
- be prone to arbitrary changes with time.
- <productname>PostgreSQL</productname> uses your operating
- system's underlying features to provide time-zone
- support, and these systems usually contain information for only
- the time period 1902 through 2038 (corresponding to the full
- range of conventional Unix system time).
- <type>timestamp with time zone</type> will use time zone
- information only within that year range, and assumes that times
- are in UTC outside that range.
- </para>
- </note>
+ <para>
+ <type>time</type> and <type>timestamp</type> both accept an
+ option precision field <replaceable>p</replaceable> which
+ determines the number of digits retained beyond the seconds
+ decimal point. By default, there is no explicit bound on precision
+ and the actual precision is determined by the underlying double
+ precision floating point number used to store values in seconds
+ for <type>interval</type> and
+ since 2000-01-01 in the case of <type>timestamp</type>.
+ </para>
+
+ <para>
+ Time zones, and time-zone conventions, are influenced by
+ political decisions, not just physical effects. Time zones have
+ become somewhat standardized around the world during the 1900's,
+ but continue to
+ be prone to arbitrary changes.
+ <productname>PostgreSQL</productname> uses your operating
+ system's underlying features to provide time-zone
+ support, and these systems usually contain information for only
+ the time period 1902 through 2038 (corresponding to the full
+ range of conventional Unix system time).
+ <type>timestamp with time zone</type> will use time zone
+ information only within that year range, and assumes that times
+ are in UTC outside that range.
</para>
<para>
To ensure compatibility to earlier versions of <productname>PostgreSQL</productname>
- we also continue to provide <type>datetime</type>
+ we continue to provide <type>datetime</type>
(equivalent to <type>timestamp</type>) and
<type>timespan</type> (equivalent to <type>interval</type>),
however support for these is now restricted to having an
Remember that any date or time input needs to be enclosed into
single quotes, like text strings. Refer to <xref
linkend="sql-syntax-constants-generic"> for more information.
- SQL requires the following syntax
+ <acronym>SQL9x</acronym> requires the following syntax
<synopsis>
-<replaceable>type</replaceable> '<replaceable>value</replaceable>'
+<replaceable>type</replaceable> [ (<replaceable>p</replaceable>) ] '<replaceable>value</replaceable>'
</synopsis>
- but <productname>PostgreSQL</productname> is more flexible.
+ where <replaceable>p</replaceable> is an integer specifying the
+ number of fractional digits in the seconds field, and is allowed
+ for <type>time</type>, <type>timestamp</type>, and <type>interval</type> types.
+ <productname>PostgreSQL</productname> is more flexible in
+ handling date/time than the
+ <acronym>SQL</acronym> standard requires.
</para>
<sect3>
</sect3>
<sect3>
- <title><type>time [ without time zone ]</type></title>
+ <title><type>time [ ( <replaceable>p</replaceable> ) ] [ without time zone ]</type></title>
<indexterm>
<primary>time</primary>
</indexterm>
<para>
- Per SQL99, this type can be referenced as <type>time</type> and
- as <type>time without time zone</type>.
+ Per SQL99, this type can be specified as <type>time</type> or
+ as <type>time without time zone</type>. The optional precision
+ <replaceable>p</replaceable> should be between 0 and 13, and
+ defaults to the precision of the input time literal.
</para>
<para>
</sect3>
<sect3>
- <title><type>time with time zone</type></title>
+ <title><type>time [ ( <replaceable>precision</replaceable> ) ] with time zone</type></title>
<indexterm>
<primary>time with time zone</primary>
required by any application.
</para>
+ <para>
+ The optional precision
+ <replaceable>p</replaceable> should be between 0 and 13, and
+ defaults to the precision of the input time literal.
+ </para>
+
<para>
<type>time with time zone</type> accepts all input also legal
for the <type>time</type> type, appended with a legal time zone,
</sect3>
<sect3>
- <title><type>timestamp without time zone</type></title>
+ <title><type>timestamp [ (<replaceable>precision</replaceable>) ] without time zone</type></title>
<indexterm>
<primary>timestamp without time zone</primary>
</indexterm>
<para>
- Valid input for the <type>timestamp without time zone</type>
+ Valid input for the <type>timestamp [ (<replaceable>p</replaceable>) ] without time zone</type>
type consists of a concatenation
of a date and a time, followed by an optional <literal>AD</literal> or
<literal>BC</literal>, followed by an optional time zone. (See below.)
is supported.
</para>
+ <para>
+ The optional precision
+ <replaceable>p</replaceable> should be between 0 and 13, and
+ defaults to the precision of the input <type>timestamp</type> literal.
+ </para>
+
<para>
For <type>timestamp without time zone</type>, any explicit time
zone specified in the input is silently swallowed. That is, the
</sect3>
<sect3>
- <title><type>timestamp with time zone</type></title>
+ <title><type>timestamp [ (<replaceable>precision</replaceable>) ] with time zone</type></title>
<indexterm>
<primary>timestamp</primary>
is supported.
</para>
+ <para>
+ The optional precision
+ <replaceable>p</replaceable> should be between 0 and 13, and
+ defaults to the precision of the input <type>timestamp</type> literal.
+ </para>
+
<para>
<table tocentry="1" id="datatype-timezone-table">
<title>Time Zone Input</title>
The following <acronym>SQL</acronym>-compatible functions can be
used as date or time
input for the corresponding data type: <literal>CURRENT_DATE</literal>,
- <literal>CURRENT_TIME</literal>, <literal>CURRENT_TIMESTAMP</literal>.
+ <literal>CURRENT_TIME</literal>,
+ <literal>CURRENT_TIMESTAMP</literal>. The latter two accept an
+ optional precision specification.
</para>
<para>
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.36 2001/11/21 05:53:41 thomas Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.37 2001/12/08 03:24:22 thomas Exp $ -->
<appendix id="docguide">
<title>Documentation</title>
<para>
The hardcopy Postscript documentation is generated by converting the
<acronym>SGML</acronym> source code to <acronym>RTF</acronym>, then
- importing into <productname>ApplixWare-4.4.1</productname>.
+ importing into <productname>ApplixWare</productname>.
After a little cleanup (see the following
section) the output is <quote>printed</quote> to a postscript file.
</para>
<step performance="required">
<para>
Repair the RTF file to correctly specify all
- styles, in particular the default style. The field can be added
- using <application>vi</application> or the following small
- <application>sed</application> procedure:
+ styles, in particular the default style. If the document
+ contains <sgmltag>REFENTRY</sgmltag> sections, one must also
+ replace formatting hints which tie a
+ <emphasis>preceeding</emphasis> paragraph to the current
+ paragraph, and instead tie the current paragraph to the
+ following one. A utility, <application>fixrtf</application> is
+ available in
+ <filename>doc/src/sgml</filename> to accomplish these repairs:
+
+ <programlisting>
+% cd doc/src/sgml
+% fixrtf tutorial.rtf
+ </programlisting>
- <programlisting>
-#!/bin/sh
-# fixrtf.sh
-# Utility to repair slight damage in RTF files generated by jade
-# Thomas Lockhart <lockhart@alumni.caltech.edu>
-#
-for i in $* ; do
- mv $i $i.orig
- cat $i.orig | sed 's#\\stylesheet#\\stylesheet{\\s0 Normal;}#' > $i
-done
-
-exit
- </programlisting>
+ or
+
+ <programlisting>
+% cd doc/src/sgml
+% fixrtf --refentry reference.rtf
+ </programlisting>
+ </para>
- where the script is adding <literal>{\s0 Normal;}</literal> as
+ <para>
+ The script adds <literal>{\s0 Normal;}</literal> as
the zero-th style in the document. According to ApplixWare, the
RTF standard would prohibit adding an implicit zero-th style,
- though M$Word happens to handle this case.
+ though M$Word happens to handle this case. For repairing
+ <sgmltag>REFENTRY</sgmltag> sections, the script replaces
+ <literal>\keepn</literal> tags with <literal>\keep</literal>.
</para>
</step>
<literal>TOC-Heading 1</literal>
</entry>
<entry>
- <literal>0.6</literal>
+ <literal>0.4</literal>
</entry>
<entry>
- <literal>0.6</literal>
+ <literal>0.4</literal>
</entry>
</row>
<literal>TOC-Heading 2</literal>
</entry>
<entry>
- <literal>1.0</literal>
+ <literal>0.8</literal>
</entry>
<entry>
- <literal>1.0</literal>
+ <literal>0.8</literal>
</entry>
</row>
<literal>TOC-Heading 3</literal>
</entry>
<entry>
- <literal>1.4</literal>
+ <literal>1.2</literal>
</entry>
<entry>
- <literal>1.4</literal>
+ <literal>1.2</literal>
</entry>
</row>
</tbody>
</para>
</step>
+<!--
+Later stylesheets seem to not need this adjustment - thomas 2001-11-29
<step performance="required">
<para>
If a bibliography is present, remove the <firstterm>short
information immediately following.
</para>
</step>
+-->
+
+ <step performance="optional">
+ <para>
+ Delete the index section from the document if it is empty.
+ </para>
+ </step>
+
+ <step performance="required">
+ <para>
+ Regenerate and adjust the table of contents.
+ </para>
+
+ <substeps>
+ <step>
+ <para>
+ Select the ToC field.
+ </para>
+ </step>
+
+ <step>
+ <para>
+ Select
+ <literal>Tools->Book Building->Create Table of
+ Contents</literal>.
+ </para>
+ </step>
+
+ <step>
+ <para>
+ Unbind the ToC by selecting
+ <literal>Tools->Field Editing->Unprotect</literal>.
+ </para>
+ </step>
+
+ <step>
+ <para>
+ Delete the first line in the ToC, which is an entry for the
+ ToC itself.
+ </para>
+ </step>
+ </substeps>
+ </step>
<step performance="required">
<para>
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.68 2001/12/04 02:21:35 tgl Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.69 2001/12/08 03:24:22 thomas Exp $ -->
<chapter id="installation">
<title><![%standalone-include[<productname>PostgreSQL</>]]>
</thead>
<tbody>
<row>
- <entry><systemitem class="osname">AIX 4.3.3</></entry>
+ <entry><systemitem class="osname">AIX</></entry>
<entry><systemitem>RS6000</></entry>
- <entry>7.1</entry>
- <entry>2001-03-21, Gilles Darold (<email>gilles@darold.net</email>)</entry>
- <entry>see also <filename>doc/FAQ_AIX</filename></entry>
+ <entry>7.2</entry>
+ <entry>2001-11-28,
+ Andreas Zeugswetter (<email>ZeugswetterA@spardat.at</email>)</entry>
+ <entry>4.3; see also <filename>doc/FAQ_AIX</filename></entry>
</row>
<row>
- <entry><systemitem class="osname">BeOS 5.0.4</></entry>
+ <entry><systemitem class="osname">BeOS</></entry>
<entry><systemitem>x86</></entry>
- <entry>7.1</entry>
- <entry>2001-02-26, Cyril Velter (<email>cyril.velter@libertysurf.fr</email>)</entry>
- <entry>requires new BONE networking stack</entry>
+ <entry>7.2</entry>
+ <entry>2001-11-29,
+ Cyril Velter (<email>cyril.velter@libertysurf.fr</email>)</entry>
+ <entry>5.0.4</entry>
</row>
<row>
- <entry><systemitem class="osname">BSD/OS 4.2</></entry>
+ <entry><systemitem class="osname">BSD/OS</></entry>
<entry><systemitem>x86</></entry>
<entry>7.2</entry>
- <entry>2001-11-27, Bruce Momjian (<email>pgman@candle.pha.pa.us</email>)</entry>
- <entry></entry>
+ <entry>2001-11-27,
+ Bruce Momjian (<email>pgman@candle.pha.pa.us</email>)</entry>
+ <entry>4.2</entry>
</row>
<row>
<entry><systemitem class="osname">FreeBSD</></entry>
<entry><systemitem>x86</></entry>
<entry>7.2</entry>
- <entry>2001-11-14, Chris Kings-Lynne
- (<email>chriskl@familyhealth.com.au</email>)</entry>
+ <entry>2001-11-14,
+ Chris Kings-Lynne (<email>chriskl@familyhealth.com.au</email>)</entry>
<entry></entry>
</row>
<row>
<entry><systemitem class="osname">HP-UX</></entry>
<entry><systemitem>PA-RISC</></entry>
<entry>7.2</entry>
- <entry>2001-11-16, 10.20 Tom Lane (<email>tgl@sss.pgh.pa.us</email>),
- 2001-03-22, 11.00, 11i Giles Lean (<email>giles@nemeton.com.au</email>)</entry>
- <entry>32- and 64-bit on 11.00; see also <filename>doc/FAQ_HPUX</filename></entry>
+ <entry>2001-11-29,
+ Joseph Conway (<email>Joseph.Conway@home.com</email>),
+ Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
+ <entry>11.00 and 10.20; see also <filename>doc/FAQ_HPUX</filename></entry>
</row>
<row>
- <entry><systemitem class="osname">IRIX 6.5.11</></entry>
+ <entry><systemitem class="osname">IRIX</></entry>
<entry><systemitem>MIPS</></entry>
- <entry>7.1</entry>
- <entry>2001-03-22, Robert Bruccoleri (<email>bruc@acm.org</email>)</entry>
- <entry>32-bit compilation model</entry>
+ <entry>7.2</entry>
+ <entry>2001-11-28,
+ Luis Amigo (<email>lamigo@atc.unican.es</email>)</entry>
+ <entry>6.5.13, MIPSPro 7.30</entry>
</row>
<row>
- <entry><systemitem class="osname">Linux 2.2.18</></entry>
+ <entry><systemitem class="osname">Linux</></entry>
<entry><systemitem>Alpha</></entry>
<entry>7.2</entry>
- <entry>2001-11-16, Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
- <entry>Tested at SourceForge</entry>
+ <entry>2001-11-16,
+ Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
+ <entry>2.2.18; tested at SourceForge</entry>
</row>
<row>
- <entry><systemitem class="osname">Linux 2.2.x</></entry>
+ <entry><systemitem class="osname">Linux</></entry>
<entry><systemitem>armv4l</></entry>
<entry>7.1</entry>
- <entry>2001-02-22, Mark Knox (<email>segfault@hardline.org</email>)</entry>
- <entry></entry>
+ <entry>2001-02-22,
+ Mark Knox (<email>markk@pixin.net</email>)</entry>
+ <entry>2.2.x</entry>
</row>
<row>
- <entry><systemitem class="osname">Linux 2.0.x</></entry>
+ <entry><systemitem class="osname">Linux</></entry>
<entry><systemitem>MIPS</></entry>
<entry>7.2</entry>
- <entry>2001-11-15, Hisao Shibuya (<email>shibuya@alpha.or.jp</>)</entry>
- <entry><productname>Cobalt Qube2</></entry>
+ <entry>2001-11-15,
+ Hisao Shibuya (<email>shibuya@alpha.or.jp</>)</entry>
+ <entry>2.0.x; <productname>Cobalt Qube2</></entry>
</row>
<row>
- <entry><systemitem class="osname">Linux 2.2.18</></entry>
+ <entry><systemitem class="osname">Linux</></entry>
<entry><systemitem>PPC74xx</></entry>
<entry>7.2</entry>
- <entry>2001-11-16, Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
- <entry>Apple G3</entry>
+ <entry>2001-11-16,
+ Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
+ <entry>2.2.18; Apple G3</entry>
</row>
<row>
<entry><systemitem class="osname">Linux</></entry>
<entry><systemitem>S/390</></entry>
<entry>7.1</entry>
- <entry>2000-11-17, Neale Ferguson (<email>Neale.Ferguson@softwareAG-usa.com</email>)</entry>
+ <entry>2000-11-17,
+ Neale Ferguson (<email>Neale.Ferguson@softwareAG-usa.com</email>)</entry>
<entry></entry>
</row>
<row>
- <entry><systemitem class="osname">Linux 2.2.15</></entry>
+ <entry><systemitem class="osname">Linux</></entry>
<entry><systemitem>Sparc</></entry>
- <entry>7.1</entry>
- <entry>2001-01-30, Ryan Kirkpatrick (<email>pgsql@rkirkpat.net</email>)</entry>
- <entry></entry>
+ <entry>7.2</entry>
+ <entry>2001-11-28,
+ Doug McNaught (<email>doug@wireboard.com</email>)</entry>
+ <entry>2.2.19</entry>
</row>
<row>
<entry><systemitem class="osname">Linux</></entry>
<entry><systemitem>x86</></entry>
<entry>7.2</entry>
- <entry>2001-11-15, Thomas Lockhart (<email>lockhart@fourpalms.org</email>)</entry>
+ <entry>2001-11-15,
+ Thomas Lockhart (<email>lockhart@fourpalms.org</email>)</entry>
<entry>2.0.x, 2.2.x, 2.4.x</entry>
</row>
<row>
<entry><systemitem class="osname">MacOS X</></entry>
<entry><systemitem>PPC</></entry>
<entry>7.2</entry>
- <entry>2001-11-16, Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
- <entry>Darwin 10.1</entry>
+ <entry>2001-11-28,
+ Gavin Sherry (<email>swm@linuxworld.com.au</email>)</entry>
+ <entry>Darwin 10.1.x</entry>
</row>
<row>
- <entry><systemitem class="osname">NetBSD 1.5W</></entry>
+ <entry><systemitem class="osname">NetBSD</></entry>
<entry><systemitem>Alpha</></entry>
<entry>7.2</entry>
- <entry>2001-11-20, Thomas Thai (<email>tom@minnesota.com</email>)</entry>
- <entry></entry>
+ <entry>2001-11-20,
+ Thomas Thai (<email>tom@minnesota.com</email>)</entry>
+ <entry>1.5W</entry>
</row>
<row>
- <entry><systemitem class="osname">NetBSD 1.5E</></entry>
+ <entry><systemitem class="osname">NetBSD</></entry>
<entry><systemitem>arm32</></entry>
<entry>7.1</entry>
- <entry>2001-03-21, Patrick Welche (<email>prlw1@cam.ac.uk</email>)</entry>
- <entry></entry>
+ <entry>2001-03-21,
+ Patrick Welche (<email>prlw1@cam.ac.uk</email>)</entry>
+ <entry>1.5E</entry>
</row>
<row>
<entry><systemitem class="osname">NetBSD</></entry>
<entry><systemitem>m68k</></entry>
<entry>7.0</entry>
- <entry>2000-04-10, Henry B. Hotz (<email>hotz@jpl.nasa.gov</email>)</entry>
+ <entry>2000-04-10,
+ Henry B. Hotz (<email>hotz@jpl.nasa.gov</email>)</entry>
<entry>Mac 8xx</entry>
</row>
<row>
<entry><systemitem class="osname">NetBSD</></entry>
<entry><systemitem>PPC</></entry>
- <entry>7.1</entry>
- <entry>2001-04-05, Henry B. Hotz (<email>hotz@jpl.nasa.gov</email>)</entry>
- <entry>Mac G4</entry>
+ <entry>7.2</entry>
+ <entry>2001-11-28,
+ Bill Studenmund (<email>wrstuden@netbsd.org</email>)</entry>
+ <entry>1.5</entry>
</row>
<row>
<entry><systemitem class="osname">NetBSD</></entry>
<entry><systemitem>Sparc</></entry>
- <entry>7.1</entry>
- <entry>2000-04-05, Matthew Green (<email>mrg@eterna.com.au</email>)</entry>
+ <entry>7.2</entry>
+ <entry>2001-12-03,
+ Matthew Green (<email>mrg@eterna.com.au</email>)</entry>
<entry>32- and 64-bit builds</entry>
</row>
<row>
- <entry><systemitem class="osname">NetBSD 1.5</></entry>
+ <entry><systemitem class="osname">NetBSD</></entry>
<entry><systemitem>VAX</></entry>
<entry>7.1</entry>
- <entry>2001-03-30, Tom I. Helbekkmo (<email>tih@kpnQwest.no</email>)</entry>
- <entry></entry>
+ <entry>2001-03-30,
+ Tom I. Helbekkmo (<email>tih@kpnQwest.no</email>)</entry>
+ <entry>1.5</entry>
</row>
<row>
- <entry><systemitem class="osname">NetBSD 1.5</></entry>
+ <entry><systemitem class="osname">NetBSD</></entry>
<entry><systemitem>x86</></entry>
- <entry>7.1</entry>
- <entry>2001-03-23, Giles Lean (<email>giles@nemeton.com.au</email>)</entry>
- <entry></entry>
+ <entry>7.2</entry>
+ <entry>2001-11-28,
+ Bill Studenmund (<email>wrstuden@netbsd.org</email>)</entry>
+ <entry>1.5</entry>
</row>
<row>
- <entry><systemitem class="osname">OpenBSD 2.8</></entry>
+ <entry><systemitem class="osname">OpenBSD</></entry>
<entry><systemitem>Sparc</></entry>
- <entry>7.1</entry>
- <entry>2001-03-23, Brandon Palmer (<email>bpalmer@crimelabs.net</email>)</entry>
- <entry></entry>
+ <entry>7.2</entry>
+ <entry>2001-11-27,
+ Brandon Palmer (<email>bpalmer@crimelabs.net</email>)</entry>
+ <entry>OBSD-3.0</entry>
</row>
<row>
- <entry><systemitem class="osname">OpenBSD 2.8</></entry>
+ <entry><systemitem class="osname">OpenBSD</></entry>
<entry><systemitem>x86</></entry>
- <entry>7.1</entry>
- <entry>2001-03-21, Brandon Palmer (<email>bpalmer@crimelabs.net</email>)</entry>
- <entry></entry>
+ <entry>7.2</entry>
+ <entry>2001-11-26,
+ Brandon Palmer (<email>bpalmer@crimelabs.net</email>)</entry>
+ <entry>OBSD-3.0</entry>
</row>
<row>
- <entry><systemitem class="osname">SCO UnixWare 7.1.1</></entry>
+ <entry><systemitem class="osname">OpenUnix</></entry>
<entry><systemitem>x86</></entry>
- <entry>7.1</entry>
- <entry>2001-03-19, Larry Rosenman (<email>ler@lerctr.org</email>)</entry>
- <entry><productname>UDK FS</productname> compiler; see also <filename>doc/FAQ_SCO</filename></entry>
+ <entry>7.2</entry>
+ <entry>2001-11-28,
+ OU-8 Larry Rosenman (<email>ler@lerctr.org</email>),
+ UW-7 Olivier Prenant (<email>ohp@pyrenet.fr</email>)</entry>
+ <entry>see also <filename>doc/FAQ_SCO</filename></entry>
</row>
+ <row>
+ <entry><systemitem class="osname">QNX 4.25</></entry>
+ <entry><systemitem>x86</></entry>
+ <entry>7.1</entry>
+ <entry>2001-05-24,
+ Bernd Tegge (<email>tegge@repas-aeg.de</email>)
+ </entry>
+ <entry>7.2 w/patches on QNX 6; see also <filename>doc/FAQ_QNX4</filename></entry>
+ </row>
<row>
<entry><systemitem class="osname">Solaris</></entry>
<entry><systemitem>Sparc</></entry>
<entry>7.2</entry>
- <entry>2001-11-12, Andrew Sullivan (<email>andrew@libertyrms.com</email>)</entry>
+ <entry>2001-11-12,
+ Andrew Sullivan (<email>andrew@libertyrms.com</email>)</entry>
<entry>2.6-8; see also <filename>doc/FAQ_Solaris</filename></entry>
</row>
<row>
- <entry><systemitem class="osname">Solaris 2.8</></entry>
+ <entry><systemitem class="osname">Solaris</></entry>
<entry><systemitem>x86</></entry>
- <entry>7.1</entry>
- <entry>2001-03-27, Mathijs Brands (<email>mathijs@ilse.nl</email>)</entry>
- <entry>see also <filename>doc/FAQ_Solaris</filename></entry>
+ <entry>7.2</entry>
+ <entry>2001-11-28,
+ Martin Renters (<email>martin@datafax.com</email>)</entry>
+ <entry>2.8; see also <filename>doc/FAQ_Solaris</filename></entry>
</row>
+<!--
+No longer compiles without error, but not really needing to be listed
+as unsupported either since it is superceded by Solaris. - thomas 2001-12-03
<row>
- <entry><systemitem class="osname">SunOS 4.1.4</></entry>
+ <entry><systemitem class="osname">SunOS</></entry>
<entry><systemitem>Sparc</></entry>
<entry>7.1</entry>
- <entry>2001-03-23, Tatsuo Ishii (<email>t-ishii@sra.co.jp</email>)</entry>
- <entry></entry>
+ <entry>2001-03-23,
+ Tatsuo Ishii (<email>t-ishii@sra.co.jp</email>)</entry>
+ <entry>4.1.4</entry>
</row>
+-->
<row>
- <entry><systemitem class="osname">Tru64 UNIX</></entry>
+ <entry><systemitem class="osname">Tru64</></entry>
<entry><systemitem>Alpha</></entry>
- <entry>7.1</entry>
- <entry>2001-03-26, Adriaan Joubert (<email>a.joubert@albourne.com</email>)</entry>
- <entry>4.0-5.0, <command>cc</> and <command>gcc</></entry>
+ <entry>7.2</entry>
+ <entry>2001-11-26,
+ Alessio Bragadini (<email>alessio@albourne.com</email>)</entry>
+ <entry>4.0g, with cc and gcc</entry>
</row>
<row>
- <entry><systemitem class="osname">Windows NT/2000</> with <application>Cygwin</></entry>
+ <entry><systemitem class="osname">Windows NT/2000</></entry>
<entry><systemitem>x86</></entry>
<entry>7.1</entry>
- <entry>2001-03-16, Jason Tishler (<email>Jason.Tishler@dothill.com</email>)</entry>
+ <entry>2001-03-16,
+ Jason Tishler (<email>jason@tishler.net</email>)</entry>
<entry>with <application>Cygwin</application> tool set, see <filename>doc/FAQ_MSWIN</filename></entry>
</row>
</tbody>
<entry>1998-03-01, Brian E Gallew (<email>geek+@cmu.edu</email>)</entry>
<entry>6.4 probably OK</entry>
</row>
+<!--
+Obsolete platform? This distro was merged into PPC afaik. - thomas 2001-12-07
<row>
<entry><systemitem class="osname">MkLinux DR1</></entry>
<entry><systemitem>PPC750</></entry>
<entry>2001-04-03, Tatsuo Ishii (<email>t-ishii@sra.co.jp</email>)</entry>
<entry>7.1 needs OS update?</entry>
</row>
+-->
<row>
<entry><systemitem class="osname">NextStep</></entry>
<entry><systemitem>x86</></entry>
<entry>1998-03-01, David Wetzel (<email>dave@turbocat.de</email>)</entry>
<entry>bit rot suspected</entry>
</row>
- <row>
- <entry><systemitem class="osname">QNX 4.25</></entry>
- <entry><systemitem>x86</></entry>
- <entry>7.0</entry>
- <entry>2000-04-01, Dr. Andreas Kardos (<email>kardos@repas-aeg.de</email>)</entry>
- <entry>Spinlock code needs work. See also <filename>doc/FAQ_QNX4</filename>.</entry>
- </row>
<row>
<entry><systemitem class="osname">SCO OpenServer 5</></entry>
<entry><systemitem>x86</></entry>
<entry><systemitem>VAX</></entry>
<entry>6.x</entry>
<entry>1998-03-01</entry>
- <entry>No recent reports. Obsolete?</entry>
+ <entry>No recent reports</entry>
</row>
<row>
<entry><systemitem class="osname">Windows 9x, ME, NT, 2000</> (native)</entry>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.54 2001/12/01 04:19:20 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.55 2001/12/08 03:24:23 thomas Exp $
-->
<chapter id="sql-syntax">
<programlisting>
SELECT 'foo' 'bar';
</programlisting>
- is not valid syntax.
+ is not valid syntax, and <productname>PostgreSQL</productname> is
+ consistant with <acronym>SQL9x</acronym> in this regard.
</para>
</sect3>
<para>
Integer constants in SQL are sequences of decimal digits (0
- though 9) with no decimal point. The range of legal values
+ though 9) with no decimal point and no exponent. The range of legal values
depends on which integer data type is used, but the plain
<type>integer</type> type accepts values ranging from -2147483648
to +2147483647. (The optional plus or minus sign is actually a
</synopsis>
where <replaceable>digits</replaceable> is one or more decimal
digits. At least one digit must be before or after the decimal
- point, and after the <literal>e</literal> if you use that option.
+ point. At least one digit must follow the exponent delimiter
+ (<literal>e</literal>) if that field is present.
Thus, a floating point constant is distinguished from an integer
constant by the presence of either the decimal point or the
exponent clause (or both). There must not be a space or other
characters embedded in the constant.
</para>
- <informalexample>
- <para>
- These are some examples of valid floating point constants:
-<literallayout>
+ <informalexample>
+ These are some examples of valid floating point constants:
+ <literallayout>
3.5
4.
.001
5e2
1.925e-3
-</literallayout>
- </para>
- </informalexample>
+ </literallayout>
+ </para>
+ </informalexample>
<para>
Floating point constants are of type <type>DOUBLE
by using <acronym>SQL</acronym> string notation or
<productname>PostgreSQL</productname> type notation:
-<programlisting>
REAL '1.23' -- string style
-'1.23'::REAL -- Postgres (historical) style
- </programlisting>
- </para>
- </sect3>
+'1.23'::REAL -- PostgreSQL (historical) style
+ </programlisting>
+ </para>
+ </sect3>
<sect3 id="sql-syntax-constants-generic">
<title>Constants of Other Types</title>
projects / postgresql / commitdiff