rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
postgresql/doc/src/sgml/datatype.sgml

2930 lines
88 KiB
Plaintext
Raw Normal View History

Minor markup changes. Refer to (".../catalog") in the emacs hints.
2000-03-31 05:27:42 +02:00
<!--
Add more complete details on date/time keywords and parsing rules. Move some tabular information on these from the chapter on data types to the appendix on dates and times.
2002-01-04 18:02:25 +01:00
$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.82 2002/01/04 17:02:02 thomas Exp $
Minor markup changes. Refer to (".../catalog") in the emacs hints.
2000-03-31 05:27:42 +02:00
-->
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<chapter id="datatype">
Minor updates for release.
1999-06-14 09:36:12 +02:00
<title id="datatype-title">Data Types</title>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm zone="datatype">
<primary>data types</primary>
</indexterm>
<indexterm>
<primary>types</primary>
<see>data types</see>
</indexterm>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</productname> has a rich set of native data
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
types available to users.
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
Users may add new types to <productname>PostgreSQL</productname> using the
Change DEFINE TYPE to CREATE TYPE.
2000-04-13 23:44:25 +02:00
<command>CREATE TYPE</command> command.
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</para>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<para>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<xref linkend="datatype-table"> shows all general-purpose data types
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
included in the standard distribution. Most of the alternative names
listed in the
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<quote>Aliases</quote> column are the names used internally by
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</productname> for historical reasons. In
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
addition, some internally used or deprecated types are available,
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
but they are not listed here.
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</para>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<para>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<table id="datatype-table">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Data Types</title>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<tgroup cols="3">
<thead>
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>Type Name</entry>
<entry>Aliases</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<entry>Description</entry>
</row>
</thead>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<tbody>
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>bigint</type></entry>
<entry><type>int8</type></entry>
<entry>signed eight-byte integer</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<row>
<entry><type>bigserial</type></entry>
<entry><type>serial8</type></entry>
<entry>autoincrementing eight-byte integer</entry>
</row>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>bit</type></entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<entry></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>fixed-length bit string</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>bit varying(<replaceable>n</replaceable>)</type></entry>
<entry><type>varbit(<replaceable>n</replaceable>)</type></entry>
<entry>variable-length bit string</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>boolean</type></entry>
<entry><type>bool</type></entry>
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<entry>logical Boolean (true/false)</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>box</type></entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<entry></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>rectangular box in 2D plane</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Add mention of bytea data type and escaping rules.
2001-09-04 05:17:54 +02:00
<row>
<entry><type>bytea</type></entry>
<entry></entry>
<entry>binary data</entry>
</row>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>character(<replaceable>n</replaceable>)</type></entry>
<entry><type>char(<replaceable>n</replaceable>)</type></entry>
<entry>fixed-length character string</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Update for NUMERIC/DECIMAL data type.
1999-10-13 04:44:23 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>character varying(<replaceable>n</replaceable>)</type></entry>
<entry><type>varchar(<replaceable>n</replaceable>)</type></entry>
<entry>variable-length character string</entry>
Update for NUMERIC/DECIMAL data type.
1999-10-13 04:44:23 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>cidr</type></entry>
<entry></entry>
<entry>IP network address</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>circle</type></entry>
<entry></entry>
<entry>circle in 2D plane</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>date</type></entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<entry></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>calendar date (year, month, day)</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>double precision</type></entry>
<entry><type>float8</type></entry>
<entry>double precision floating-point number</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>inet</type></entry>
<entry></entry>
<entry>IP host address</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>integer</type></entry>
<entry><type>int</type>, <type>int4</type></entry>
<entry>signed four-byte integer</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<row>
Document the precision arguments for date/time types per SQL9x. Update the list of recognized time zones. Document the range of arguments allowed for SET TIME ZONE. Still need to add info on other date/time symbols (e.g. "AM", "T") and to freshen the docs on the date/time parsing rules.
2001-12-29 19:35:54 +01:00
<entry><type>interval(<replaceable>p</replaceable>)</type></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry></entry>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<entry>general-use time span</entry>
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>line</type></entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<entry></entry>
<entry>infinite line in 2D plane</entry>
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>lseg</type></entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<entry></entry>
<entry>line segment in 2D plane</entry>
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>macaddr</type></entry>
<entry></entry>
<entry>MAC address</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Update for NUMERIC/DECIMAL data type.
1999-10-13 04:44:23 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>money</type></entry>
<entry></entry>
<entry>US-style currency</entry>
Update for NUMERIC/DECIMAL data type.
1999-10-13 04:44:23 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Document the precision arguments for date/time types per SQL9x. Update the list of recognized time zones. Document the range of arguments allowed for SET TIME ZONE. Still need to add info on other date/time symbols (e.g. "AM", "T") and to freshen the docs on the date/time parsing rules.
2001-12-29 19:35:54 +01:00
<entry><type>numeric [ (<replaceable>p</replaceable>,
<replaceable>s</replaceable>) ]</type></entry>
<entry><type>decimal [ (<replaceable>p</replaceable>,
<replaceable>s</replaceable>) ]</type></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>exact numeric with selectable precision</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>oid</type></entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<entry></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>object identifier</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>path</type></entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<entry></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>open and closed geometric path in 2D plane</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>point</type></entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<entry></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>geometric point in 2D plane</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Documentation updates to reflect TOAST and new-style fmgr.
2000-08-25 01:36:29 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>polygon</type></entry>
Documentation updates to reflect TOAST and new-style fmgr.
2000-08-25 01:36:29 +02:00
<entry></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>closed geometric path in 2D plane</entry>
Documentation updates to reflect TOAST and new-style fmgr.
2000-08-25 01:36:29 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>real</type></entry>
<entry><type>float4</type></entry>
<entry>single precision floating-point number</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>smallint</type></entry>
<entry><type>int2</type></entry>
<entry>signed two-byte integer</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>serial</type></entry>
Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
2001-08-16 22:38:56 +02:00
<entry><type>serial4</type></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>autoincrementing four-byte integer</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry><type>text</type></entry>
<entry></entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<entry>variable-length character string</entry>
</row>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<entry><type>time [ (<replaceable>p</replaceable>) ] [ without time zone ]</type></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry></entry>
<entry>time of day</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<entry><type>time [ (<replaceable>p</replaceable>) ] with time zone</type></entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry><type>timetz</type></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>time of day, including time zone</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
<row>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<entry><type>timestamp [ (<replaceable>p</replaceable>) ] without time zone</type></entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry><type>timestamp</type></entry>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
<entry>date and time</entry>
</row>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<row>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<entry><type>timestamp [ (<replaceable>p</replaceable>) ] [ with time zone ]</type></entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry><type>timestamptz</type></entry>
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
<entry>date and time, including time zone</entry>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
</row>
</tbody>
</tgroup>
</table>
</para>
Include new cidr and inet data types.
1998-10-27 07:14:41 +01:00
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<note>
<title>Compatibility</title>
<para>
The following types (or spellings thereof) are specified by SQL:
<type>bit</type>, <type>bit varying</type>, <type>boolean</type>,
<type>char</type>, <type>character</type>, <type>character
varying</type>, <type>varchar</type>, <type>date</type>,
<type>double precision</type>, <type>integer</type>,
<type>interval</type>, <type>numeric</type>, <type>decimal</type>,
<type>real</type>, <type>smallint</type>, <type>time</type>,
<type>timestamp</type> (both with or without time zone).
</para>
</note>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<para>
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
Each data type has an external representation determined by its input
and output functions. Many of the built-in types have
obvious external formats. However, several types are either unique
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
to <productname>PostgreSQL</productname>, such as open and closed
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
paths, or have several possibilities for formats, such as the date
and time types.
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
Most of the input and output functions corresponding to the
base types (e.g., integers and floating point numbers) do some
error-checking.
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
Some of the input and output functions are not invertible. That is,
the result of an output function may lose precision when compared to
the original input.
</para>
<para>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
Some of the operators and functions (e.g.,
addition and multiplication) do not perform run-time error-checking in the
interests of improving execution speed.
On some systems, for example, the numeric operators for some data types may
silently underflow or overflow.
</para>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect1 id="datatype-numeric">
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<title>Numeric Types</title>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm zone="datatype-numeric">
<primary>data types</primary>
<secondary>numeric</secondary>
</indexterm>
<indexterm zone="datatype-numeric">
<primary>integer</primary>
</indexterm>
<indexterm zone="datatype-numeric">
<primary>smallint</primary>
</indexterm>
<indexterm zone="datatype-numeric">
<primary>bigint</primary>
</indexterm>
<indexterm>
<primary>int4</primary>
<see>integer</see>
</indexterm>
<indexterm>
<primary>int2</primary>
<see>smallint</see>
</indexterm>
<indexterm>
<primary>int8</primary>
<see>bigint</see>
</indexterm>
<indexterm zone="datatype-numeric">
<primary>numeric (data type)</primary>
</indexterm>
<indexterm>
<primary>decimal</primary>
<see>numeric</see>
</indexterm>
<indexterm zone="datatype-numeric">
<primary>real</primary>
</indexterm>
<indexterm zone="datatype-numeric">
<primary>double precision</primary>
</indexterm>
<indexterm>
<primary>float4</primary>
<see>real</see>
</indexterm>
<indexterm>
<primary>float8</primary>
<see>double precision</see>
</indexterm>
<indexterm zone="datatype-numeric">
<primary>floating point</primary>
</indexterm>
Include mention of CASE, COALESCE, and IFNULL. Add date/time parsing procedure (perhaps should be in appendix). Add time zone information (ditto). Update keyword list.
1999-05-12 09:32:47 +02:00
<para>
Documentation updates to reflect TOAST and new-style fmgr.
2000-08-25 01:36:29 +02:00
Numeric types consist of two-, four-, and eight-byte integers,
four- and eight-byte
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
floating point numbers and fixed-precision decimals.
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
</para>
Add mention of the SERIAL data type. Change claim of "no limit" on maximum date for datetime type to more realistic 1465001 AD. Thanks Tatsuo for pointing this out :) Clean up markup.
1998-10-14 18:26:31 +02:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
<table tocentry="1">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Numeric Types</title>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<tgroup cols="4">
<thead>
<row>
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<entry>Type name</entry>
<entry>Storage size</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>Description</entry>
<entry>Range</entry>
</row>
</thead>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<tbody>
Update for NUMERIC/DECIMAL data type.
1999-10-13 04:44:23 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>smallint</></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>2 bytes</entry>
<entry>Fixed-precision</entry>
<entry>-32768 to +32767</entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>integer</></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>4 bytes</entry>
<entry>Usual choice for fixed-precision</entry>
<entry>-2147483648 to +2147483647</entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>bigint</></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>8 bytes</entry>
<entry>Very large range fixed-precision</entry>
Tweak int8in to accept -9223372036854775808, per recent discussion in pgsql-patches.
2001-11-24 20:57:06 +01:00
<entry>-9223372036854775808 to 9223372036854775807</entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>decimal</></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>variable</entry>
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<entry>user-specified precision, exact</entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>no limit</entry>
Update for NUMERIC/DECIMAL data type.
1999-10-13 04:44:23 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>numeric</></entry>
Update for NUMERIC/DECIMAL data type.
1999-10-13 04:44:23 +02:00
<entry>variable</entry>
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<entry>user-specified precision, exact</entry>
Update for NUMERIC/DECIMAL data type.
1999-10-13 04:44:23 +02:00
<entry>no limit</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</row>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>real</></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>4 bytes</entry>
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<entry>variable-precision, inexact</entry>
<entry>6 decimal digits precision</entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>double precision</></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>8 bytes</entry>
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<entry>variable-precision, inexact</entry>
<entry>15 decimal digits precision</entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
</row>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>serial</></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>4 bytes</entry>
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<entry>autoincrementing integer</entry>
Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
2001-08-16 22:38:56 +02:00
<entry>1 to 2147483647</entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>bigserial</type></entry>
Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
2001-08-16 22:38:56 +02:00
<entry>8 bytes</entry>
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<entry>autoincrementing integer</entry>
Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
2001-08-16 22:38:56 +02:00
<entry>1 to 9223372036854775807</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</row>
</tbody>
</tgroup>
</table>
</para>
Add mention of the SERIAL data type. Change claim of "no limit" on maximum date for datetime type to more realistic 1465001 AD. Thanks Tatsuo for pointing this out :) Clean up markup.
1998-10-14 18:26:31 +02:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Add some links from data type chapter to section on literal constants.
2001-01-26 23:04:22 +01:00
The syntax of constants for the numeric types is described in
<xref linkend="sql-syntax-constants">. The numeric types have a
full set of corresponding arithmetic operators and
functions. Refer to <xref linkend="functions"> for more
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
information. The following sections describe the types in detail.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<sect2 id="datatype-int">
<title>The Integer Types</title>
<para>
The types <type>smallint</type>, <type>integer</type>,
<type>bigint</type> store whole numbers, that is, numbers without
fractional components, of various ranges. Attempts to store
values outside of the allowed range will result in an error.
</para>
<para>
The type <type>integer</type> is the usual choice, as it offers
the best balance between range, storage size, and performance.
The <type>smallint</type> type is generally only used if disk
space is at a premium. The <type>bigint</type> type should only
be used if the <type>integer</type> range is not sufficient,
because the latter is definitely faster.
</para>
<para>
The <type>bigint</type> type may not function correctly on all
platforms, since it relies on compiler support for eight-byte
integers. On a machine without such support, <type>bigint</type>
acts the same as <type>integer</type> (but still takes up eight
bytes of storage). However, we are not aware of any reasonable
platform where this is actually the case.
</para>
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
<para>
SQL only specifies the integer types <type>integer</type> (or
<type>int</type>) and <type>smallint</type>. The type
<type>bigint</type>, and the type names <type>int2</type>,
<type>int4</type>, and <type>int8</type> are extensions, which
are shared with various other RDBMS products.
</para>
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<note>
<para>
If you have a column of type <type>smallint</type> or
<type>bigint</type> with an index, you may encounter problems
getting the system to use that index. For instance, a clause of
the form
<programlisting>
... WHERE smallint_column = 42
</programlisting>
will not use an index, because the system assigns type
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<type>integer</type> to the constant 42, and
<productname>PostgreSQL</productname> currently
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
cannot use an index when two different data types are involved. A
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
workaround is to single-quote the constant, thus:
<programlisting>
... WHERE smallint_column = '42'
</programlisting>
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
This will cause the system to delay type resolution and will
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
assign the right type to the constant.
</para>
</note>
</sect2>
<sect2 id="datatype-numeric-decimal">
<title>Arbitrary Precision Numbers</title>
<para>
The type <type>numeric</type> can store numbers of practically
unlimited size and precision, while being able to store all
numbers and carry out all calculations exactly. It is especially
recommended for storing monetary amounts and other quantities
where exactness is required. However, the <type>numeric</type>
type is very slow compared to the floating point types described
in the next section.
</para>
<para>
In what follows we use these terms: The
<firstterm>scale</firstterm> of a <type>numeric</type> is the
count of decimal digits in the fractional part, to the right of
the decimal point. The <firstterm>precision</firstterm> of a
<type>numeric</type> is the total count of significant digits in
the whole number, that is, the number of digits to both sides of
the decimal point. So the number 23.5141 has a precision of 6
and a scale of 4. Integers can be considered to have a scale of
zero.
</para>
<para>
Both the precision and the scale of the numeric type can be
configured. To declare a column of type <type>numeric</type> use
the syntax
<programlisting>
NUMERIC(<replaceable>precision</replaceable>, <replaceable>scale</replaceable>)
</programlisting>
The precision must be positive, the scale zero or positive.
Alternatively,
<programlisting>
NUMERIC(<replaceable>precision</replaceable>)
</programlisting>
Tweak parser so that there is a defined representation for datatypes bpchar, bit, numeric with typmod -1. Alter format_type so that this representation is printed when the typmod is -1. This ensures that tables having such columns can be pg_dump'd and reloaded correctly. Also, remove the rather useless and non-SQL-compliant default precision and scale for type NUMERIC. A numeric column declared as such (with no precision/scale) will now have typmod -1 which means that numeric values of any precision/scale can be stored in it, without conversion to a uniform scale. This seems significantly more useful than the former behavior. Part of response to bug #513.
2001-11-12 22:04:46 +01:00
selects a scale of 0. Specifying
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<programlisting>
NUMERIC
</programlisting>
Tweak parser so that there is a defined representation for datatypes bpchar, bit, numeric with typmod -1. Alter format_type so that this representation is printed when the typmod is -1. This ensures that tables having such columns can be pg_dump'd and reloaded correctly. Also, remove the rather useless and non-SQL-compliant default precision and scale for type NUMERIC. A numeric column declared as such (with no precision/scale) will now have typmod -1 which means that numeric values of any precision/scale can be stored in it, without conversion to a uniform scale. This seems significantly more useful than the former behavior. Part of response to bug #513.
2001-11-12 22:04:46 +01:00
without any precision or scale creates a column in which numeric
values of any precision and scale can be stored, up to the implementation
limit on precision. A column of this kind will not coerce input
values to any particular scale, whereas <type>numeric</type> columns
with a declared scale will coerce input values to that scale.
proof-reading
2001-11-28 21:49:10 +01:00
(The SQL standard requires a default scale of 0, i.e., coercion to
Tweak parser so that there is a defined representation for datatypes bpchar, bit, numeric with typmod -1. Alter format_type so that this representation is printed when the typmod is -1. This ensures that tables having such columns can be pg_dump'd and reloaded correctly. Also, remove the rather useless and non-SQL-compliant default precision and scale for type NUMERIC. A numeric column declared as such (with no precision/scale) will now have typmod -1 which means that numeric values of any precision/scale can be stored in it, without conversion to a uniform scale. This seems significantly more useful than the former behavior. Part of response to bug #513.
2001-11-12 22:04:46 +01:00
integer accuracy. We find this a bit useless. If you're concerned about
portability, always specify the precision and scale explicitly.)
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
</para>
<para>
If the precision or scale of a value is greater than the declared
precision or scale of a column, the system will attempt to round
the value. If the value cannot be rounded so as to satisfy the
declared limits, an error is raised.
</para>
<para>
The types <type>decimal</type> and <type>numeric</type> are
equivalent. Both types are part of the SQL standard.
</para>
</sect2>
<sect2 id="datatype-float">
<title>Floating Point Types</title>
<para>
The data types <type>real</type> and <type>double
precision</type> are inexact, variable precision numeric types.
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
In practice, these types are usually implementations of <acronym>IEEE</acronym> 754
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
binary floating point (single and double precision,
respectively), to the extent that the underlying processor,
operating system, and compiler support it.
</para>
<para>
Inexact means that some values cannot be converted exactly to the
internal format and are stored as approximations, so that storing
and printing back out a value may show slight discrepancies.
Managing these errors and how they propagate through calculations
is the subject of an entire branch of mathematics and computer
science and will not be discussed further here, except for the
following points:
<itemizedlist>
<listitem>
<para>
If you require exact storage and calculations (such as for
monetary amounts), use the <type>numeric</type> type instead.
</para>
</listitem>
<listitem>
<para>
If you want to do complicated calculations with these types
for anything important, especially if you rely on certain
behavior in boundary cases (infinity, underflow), you should
evaluate the implementation carefully.
</para>
</listitem>
<listitem>
<para>
Comparing two floating point values for equality may or may
not work as expected.
</para>
</listitem>
</itemizedlist>
</para>
<para>
Normally, the <type>real</type> type has a range of at least
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
-1E+37 to +1E+37 with a precision of at least 6 decimal digits. The
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<type>double precision</type> type normally has a range of around
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
-1E+308 to +1E+308 with a precision of at least 15 digits. Values that
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
are too large or too small will cause an error. Rounding may
take place if the precision of an input number is too high.
Numbers too close to zero that are not representable as distinct
from zero will cause an underflow error.
</para>
</sect2>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect2 id="datatype-serial">
Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
2001-08-16 22:38:56 +02:00
<title>The Serial Types</title>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm zone="datatype-serial">
<primary>serial</primary>
</indexterm>
Grammatical corrections.
2001-10-30 21:13:44 +01:00
<indexterm zone="datatype-serial">
<primary>bigserial</primary>
</indexterm>
Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
2001-08-16 22:38:56 +02:00
<indexterm zone="datatype-serial">
<primary>serial4</primary>
</indexterm>
<indexterm zone="datatype-serial">
<primary>serial8</primary>
</indexterm>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>auto-increment</primary>
<see>serial</see>
</indexterm>
<indexterm>
<primary>sequences</primary>
<secondary>and serial type</secondary>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
The <type>serial</type> data types are not truly types, but are a
Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
2001-08-16 22:38:56 +02:00
notational convenience for setting up unique identifier columns
in tables.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
In the current implementation, specifying
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<programlisting>
Bunch of copy fitting and style sheet tweakage to get decent looking print output (from pdfjadetex). Also updated instructions to install documentation processing toolchain.
2001-10-09 20:46:00 +02:00
CREATE TABLE <replaceable class="parameter">tablename</replaceable> (
<replaceable class="parameter">colname</replaceable> SERIAL
);
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
</programlisting>
Add mention of the SERIAL data type. Change claim of "no limit" on maximum date for datetime type to more realistic 1465001 AD. Thanks Tatsuo for pointing this out :) Clean up markup.
1998-10-14 18:26:31 +02:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
is equivalent to specifying:
Add mention of the SERIAL data type. Change claim of "no limit" on maximum date for datetime type to more realistic 1465001 AD. Thanks Tatsuo for pointing this out :) Clean up markup.
1998-10-14 18:26:31 +02:00
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<programlisting>
Add mention of the SERIAL data type. Change claim of "no limit" on maximum date for datetime type to more realistic 1465001 AD. Thanks Tatsuo for pointing this out :) Clean up markup.
1998-10-14 18:26:31 +02:00
CREATE SEQUENCE <replaceable class="parameter">tablename</replaceable>_<replaceable class="parameter">colname</replaceable>_seq;
Bunch of copy fitting and style sheet tweakage to get decent looking print output (from pdfjadetex). Also updated instructions to install documentation processing toolchain.
2001-10-09 20:46:00 +02:00
CREATE TABLE <replaceable class="parameter">tablename</replaceable> (
<replaceable class="parameter">colname</replaceable> integer DEFAULT nextval('<replaceable class="parameter">tablename</replaceable>_<replaceable class="parameter">colname</replaceable>_seq') UNIQUE NOT NULL
);
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
</programlisting>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
2001-08-16 22:38:56 +02:00
Thus, we have created an integer column and arranged for its default
values to be assigned from a sequence generator. UNIQUE and NOT NULL
constraints are applied to ensure that explicitly-inserted values
will never be duplicates, either.
Bunch of copy fitting and style sheet tweakage to get decent looking print output (from pdfjadetex). Also updated instructions to install documentation processing toolchain.
2001-10-09 20:46:00 +02:00
</para>
Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
2001-08-16 22:38:56 +02:00
Bunch of copy fitting and style sheet tweakage to get decent looking print output (from pdfjadetex). Also updated instructions to install documentation processing toolchain.
2001-10-09 20:46:00 +02:00
<important>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
The implicit sequence created for the <type>serial</type> type will
<emphasis>not</emphasis> be automatically removed when the
table is dropped.
</para>
Bunch of copy fitting and style sheet tweakage to get decent looking print output (from pdfjadetex). Also updated instructions to install documentation processing toolchain.
2001-10-09 20:46:00 +02:00
</important>
Add mention of the SERIAL data type. Change claim of "no limit" on maximum date for datetime type to more realistic 1465001 AD. Thanks Tatsuo for pointing this out :) Clean up markup.
1998-10-14 18:26:31 +02:00
Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
2001-08-16 22:38:56 +02:00
<para>
The type names <type>serial</type> and <type>serial4</type> are
equivalent: both create <type>integer</type> columns. The type
Grammatical corrections.
2001-10-30 21:13:44 +01:00
names <type>bigserial</type> and <type>serial8</type> work just
the same way, except that they create a <type>bigint</type>
column. <type>bigserial</type> should be used if you anticipate
proof-reading
2001-11-28 21:49:10 +01:00
use of more than 2<superscript>31</> identifiers over the lifetime of the table.
Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
2001-08-16 22:38:56 +02:00
</para>
<para>
Grammatical corrections.
2001-10-30 21:13:44 +01:00
Implicit sequences supporting the <type>serial</type> types are
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
not automatically dropped when a table containing a serial type
is dropped. So, the following commands executed in order will likely fail:
Add mention of the SERIAL data type. Change claim of "no limit" on maximum date for datetime type to more realistic 1465001 AD. Thanks Tatsuo for pointing this out :) Clean up markup.
1998-10-14 18:26:31 +02:00
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
<programlisting>
Add mention of the SERIAL data type. Change claim of "no limit" on maximum date for datetime type to more realistic 1465001 AD. Thanks Tatsuo for pointing this out :) Clean up markup.
1998-10-14 18:26:31 +02:00
CREATE TABLE <replaceable class="parameter">tablename</replaceable> (<replaceable class="parameter">colname</replaceable> SERIAL);
DROP TABLE <replaceable class="parameter">tablename</replaceable>;
CREATE TABLE <replaceable class="parameter">tablename</replaceable> (<replaceable class="parameter">colname</replaceable> SERIAL);
Start adding some more documentation about the number types. Make bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 22:03:45 +02:00
</programlisting>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
The sequence will remain in the database until explicitly dropped using
Grammatical corrections.
2001-10-30 21:13:44 +01:00
<command>DROP SEQUENCE</command>. (This annoyance will probably be
changed in some future release.)
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
</sect2>
</sect1>
Add mention of the SERIAL data type. Change claim of "no limit" on maximum date for datetime type to more realistic 1465001 AD. Thanks Tatsuo for pointing this out :) Clean up markup.
1998-10-14 18:26:31 +02:00
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect1 id="datatype-money">
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<title>Monetary Type</title>
<note>
Add some links from data type chapter to section on literal constants.
2001-01-26 23:04:22 +01:00
<title>Deprecated</title>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
minor copy editing
2001-03-25 00:03:26 +01:00
The <type>money</type> type is deprecated. Use
Add some links from data type chapter to section on literal constants.
2001-01-26 23:04:22 +01:00
<type>numeric</type> or <type>decimal</type> instead, in
combination with the <function>to_char</function> function. The
money type may become a locale-aware layer over the
<type>numeric</type> type in a future release.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
</note>
<para>
Add some links from data type chapter to section on literal constants.
2001-01-26 23:04:22 +01:00
The <type>money</type> type stores U.S.-style currency with fixed
decimal point representation. If
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</productname> is compiled with locale
Add some links from data type chapter to section on literal constants.
2001-01-26 23:04:22 +01:00
support then the <type>money</type> type uses locale-specific
output formatting.
</para>
<para>
Input is accepted in a variety of formats, including integer and
floating point literals, as well as <quote>typical</quote>
currency formatting, such as <literal>'$1,000.00'</literal>.
Output is in the latter form.
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
</para>
Add mention of the SERIAL data type. Change claim of "no limit" on maximum date for datetime type to more realistic 1465001 AD. Thanks Tatsuo for pointing this out :) Clean up markup.
1998-10-14 18:26:31 +02:00
Remove disclaimer about exact numeric types. They work now!
1999-05-27 17:47:28 +02:00
<para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<table tocentry="1">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Monetary Types</title>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<tgroup cols="4">
<thead>
<row>
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<entry>Type Name</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>Storage</entry>
<entry>Description</entry>
<entry>Range</entry>
</row>
</thead>
<tbody>
<row>
<entry>money</entry>
<entry>4 bytes</entry>
<entry>Fixed-precision</entry>
<entry>-21474836.48 to +21474836.47</entry>
</row>
</tbody>
</tgroup>
</table>
Remove disclaimer about exact numeric types. They work now!
1999-05-27 17:47:28 +02:00
</para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</sect1>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Add some links from data type chapter to section on literal constants.
2001-01-26 23:04:22 +01:00
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect1 id="datatype-character">
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<title>Character Types</title>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm zone="datatype-character">
<primary>character strings</primary>
<secondary>data types</secondary>
</indexterm>
<indexterm>
<primary>strings</primary>
<see>character strings</see>
</indexterm>
<indexterm>
<primary>text</primary>
<see>character strings</see>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<table tocentry="1">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Character Types</title>
some clarifications inspired by the DocNotes
2001-08-08 00:41:49 +02:00
<tgroup cols="2">
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<thead>
<row>
some clarifications inspired by the DocNotes
2001-08-08 00:41:49 +02:00
<entry>Type name</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>character(<replaceable>n</>)</type>, <type>char(<replaceable>n</>)</type></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>Fixed-length blank padded</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>character varying(<replaceable>n</>)</type>, <type>varchar(<replaceable>n</>)</type></entry>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<entry>Variable-length with limit</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>text</type></entry>
Clarify the allowed length of the text data type.
2000-12-03 15:47:18 +01:00
<entry>Variable unlimited length</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</row>
Add mention of bytea data type and escaping rules.
2001-09-04 05:17:54 +02:00
</tbody>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</tgroup>
</table>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Make char(n) and varchar(n) types raise an error if the inserted string is too long. While I was adjusting the regression tests I moved the array things all into array.sql, to make things more manageable.
2001-05-21 18:54:46 +02:00
<para>
<acronym>SQL</acronym> defines two primary character types:
<type>character(<replaceable>n</>)</type> and <type>character
varying(<replaceable>n</>)</type>, where <replaceable>n</> is a
positive integer. Both of these types can store strings up to
<replaceable>n</> characters in length. An attempt to store a
longer string into a column of these types will result in an
error, unless the excess characters are all spaces, in which case
the string will be truncated to the maximum length. (This
somewhat bizarre exception is required by the SQL standard.) If
the string to be stored is shorter than the declared length,
values of type <type>character</type> will be space-padded; values
of type <type>character varying</type> will simply store the
shorter string.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
Make char(n) and varchar(n) types raise an error if the inserted string is too long. While I was adjusting the regression tests I moved the array things all into array.sql, to make things more manageable.
2001-05-21 18:54:46 +02:00
<note>
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
Prior to <productname>PostgreSQL</> 7.2, strings that were too long were silently
Make char(n) and varchar(n) types raise an error if the inserted string is too long. While I was adjusting the regression tests I moved the array things all into array.sql, to make things more manageable.
2001-05-21 18:54:46 +02:00
truncated, no error was raised.
</para>
</note>
<para>
The notations <type>char(<replaceable>n</>)</type> and
<type>varchar(<replaceable>n</>)</type> are aliases for
<type>character(<replaceable>n</>)</type> and <type>character
varying(<replaceable>n</>)</type>,
respectively. <type>character</type> without length specifier is
equivalent to <type>character(1)</type>; if <type>character
varying</type> is used without length specifier, the type accepts
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
strings of any size. The latter is a <productname>PostgreSQL</> extension.
Make char(n) and varchar(n) types raise an error if the inserted string is too long. While I was adjusting the regression tests I moved the array things all into array.sql, to make things more manageable.
2001-05-21 18:54:46 +02:00
</para>
<para>
In addition, <productname>PostgreSQL</productname> supports the
more general <type>text</type> type, which stores strings of any
length. Unlike <type>character varying</type>, <type>text</type>
does not require an explicit declared upper limit on the size of
the string. Although the type <type>text</type> is not in the SQL
standard, many other RDBMS packages have it as well.
</para>
<para>
some clarifications inspired by the DocNotes
2001-08-08 00:41:49 +02:00
The storage requirement for data of these types is 4 bytes plus
the actual string, and in case of <type>character</type> plus the
Tweak parser so that there is a defined representation for datatypes bpchar, bit, numeric with typmod -1. Alter format_type so that this representation is printed when the typmod is -1. This ensures that tables having such columns can be pg_dump'd and reloaded correctly. Also, remove the rather useless and non-SQL-compliant default precision and scale for type NUMERIC. A numeric column declared as such (with no precision/scale) will now have typmod -1 which means that numeric values of any precision/scale can be stored in it, without conversion to a uniform scale. This seems significantly more useful than the former behavior. Part of response to bug #513.
2001-11-12 22:04:46 +01:00
padding. Long strings will be compressed by the system
proof-reading
2001-11-28 21:49:10 +01:00
automatically, so the physical requirement on disk may be less.
Tweak parser so that there is a defined representation for datatypes bpchar, bit, numeric with typmod -1. Alter format_type so that this representation is printed when the typmod is -1. This ensures that tables having such columns can be pg_dump'd and reloaded correctly. Also, remove the rather useless and non-SQL-compliant default precision and scale for type NUMERIC. A numeric column declared as such (with no precision/scale) will now have typmod -1 which means that numeric values of any precision/scale can be stored in it, without conversion to a uniform scale. This seems significantly more useful than the former behavior. Part of response to bug #513.
2001-11-12 22:04:46 +01:00
In any case, the longest possible character string
some clarifications inspired by the DocNotes
2001-08-08 00:41:49 +02:00
that can be stored is about 1 GB. (The maximum value that will be
allowed for <replaceable>n</> in the data type declaration is
Tweak parser so that there is a defined representation for datatypes bpchar, bit, numeric with typmod -1. Alter format_type so that this representation is printed when the typmod is -1. This ensures that tables having such columns can be pg_dump'd and reloaded correctly. Also, remove the rather useless and non-SQL-compliant default precision and scale for type NUMERIC. A numeric column declared as such (with no precision/scale) will now have typmod -1 which means that numeric values of any precision/scale can be stored in it, without conversion to a uniform scale. This seems significantly more useful than the former behavior. Part of response to bug #513.
2001-11-12 22:04:46 +01:00
less than that. It wouldn't be very useful to change
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
this because with multibyte character encodings the number of
Tweak parser so that there is a defined representation for datatypes bpchar, bit, numeric with typmod -1. Alter format_type so that this representation is printed when the typmod is -1. This ensures that tables having such columns can be pg_dump'd and reloaded correctly. Also, remove the rather useless and non-SQL-compliant default precision and scale for type NUMERIC. A numeric column declared as such (with no precision/scale) will now have typmod -1 which means that numeric values of any precision/scale can be stored in it, without conversion to a uniform scale. This seems significantly more useful than the former behavior. Part of response to bug #513.
2001-11-12 22:04:46 +01:00
characters and bytes can be quite different anyway. If you desire
to store long strings with no specific upper limit, use <type>text</type>
or <type>character varying</type> without a length specifier,
rather than making up an arbitrary length limit.)
Make char(n) and varchar(n) types raise an error if the inserted string is too long. While I was adjusting the regression tests I moved the array things all into array.sql, to make things more manageable.
2001-05-21 18:54:46 +02:00
</para>
<tip>
<para>
There are no performance differences between these three types,
apart from the increased storage size when using the blank-padded
type.
</para>
</tip>
some clarifications inspired by the DocNotes
2001-08-08 00:41:49 +02:00
<para>
Refer to <xref linkend="sql-syntax-strings"> for information about
the syntax of string literals, and to <xref linkend="functions">
for information about available operators and functions.
</para>
Make char(n) and varchar(n) types raise an error if the inserted string is too long. While I was adjusting the regression tests I moved the array things all into array.sql, to make things more manageable.
2001-05-21 18:54:46 +02:00
<example>
<title>Using the character types</title>
<programlisting>
CREATE TABLE test1 (a character(4));
INSERT INTO test1 VALUES ('ok');
SELECT a, char_length(a) FROM test1; -- <co id="co.datatype-char">
<computeroutput>
a | char_length
------+-------------
ok | 4
</computeroutput>
CREATE TABLE test2 (b varchar(5));
INSERT INTO test2 VALUES ('ok');
INSERT INTO test2 VALUES ('good ');
INSERT INTO test2 VALUES ('too long');
<computeroutput>ERROR: value too long for type character varying(5)</computeroutput>
SELECT b, char_length(b) FROM test2;
<computeroutput>
b | char_length
-------+-------------
ok | 2
good | 5
</computeroutput>
</programlisting>
<calloutlist>
<callout arearefs="co.datatype-char">
<para>
The <function>char_length</function> function is discussed in
<xref linkend="functions-string">.
</para>
</callout>
</calloutlist>
</example>
Remove disclaimer about exact numeric types. They work now!
1999-05-27 17:47:28 +02:00
<para>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
There are two other fixed-length character types in
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</productname>. The <type>name</type> type
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
exists <emphasis>only</emphasis> for storage of internal catalog
names and is not intended for use by the general user. Its length
Tweak parser so that there is a defined representation for datatypes bpchar, bit, numeric with typmod -1. Alter format_type so that this representation is printed when the typmod is -1. This ensures that tables having such columns can be pg_dump'd and reloaded correctly. Also, remove the rather useless and non-SQL-compliant default precision and scale for type NUMERIC. A numeric column declared as such (with no precision/scale) will now have typmod -1 which means that numeric values of any precision/scale can be stored in it, without conversion to a uniform scale. This seems significantly more useful than the former behavior. Part of response to bug #513.
2001-11-12 22:04:46 +01:00
is currently defined as 32 bytes (31 usable characters plus terminator)
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
but should be referenced using the macro
<symbol>NAMEDATALEN</symbol>. The length is set at compile time
(and is therefore adjustable for special uses); the default
maximum length may change in a future release. The type
<type>"char"</type> (note the quotes) is different from
<type>char(1)</type> in that it only uses one byte of storage. It
is internally used in the system catalogs as a poor-man's
enumeration type.
Remove disclaimer about exact numeric types. They work now!
1999-05-27 17:47:28 +02:00
</para>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<table tocentry="1">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Specialty Character Type</title>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<tgroup cols="3">
<thead>
<row>
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<entry>Type Name</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>Storage</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<row>
<entry>"char"</entry>
<entry>1 byte</entry>
<entry>Single character internal type</entry>
</row>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<row>
<entry>name</entry>
<entry>32 bytes</entry>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<entry>Thirty-one character internal type</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</row>
</tbody>
</tgroup>
</table>
</sect1>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<sect1 id="datatype-binary">
<title>Binary Strings</title>
<para>
The <type>bytea</type> data type allows storage of binary strings.
</para>
<table tocentry="1">
<title>Binary String Types</title>
<tgroup cols="3">
<thead>
<row>
<entry>Type Name</entry>
<entry>Storage</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>bytea</entry>
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<entry>4 bytes plus the actual binary string</entry>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<entry>Variable (not specifically limited)
length binary string</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
A binary string is a sequence of octets that does not have either a
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
character set or collation associated with it. <type>Bytea</type>
specifically allows storing octets of zero value and other
<quote>non-printable</quote> octets.
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
</para>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<para>
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
Octets of certain values <emphasis>must</emphasis> be escaped (but all
octet values <emphasis>may</emphasis> be escaped) when used as part of
a string literal in an <acronym>SQL</acronym> statement. In general,
proof-reading
2001-11-28 21:49:10 +01:00
to escape an octet, it is converted into the three-digit octal number
Spelling and grammatical corrections.
2001-11-21 22:12:34 +01:00
equivalent of its decimal octet value, and preceded by two
backslashes. Some octet values have alternate escape sequences, as
shown in <xref linkend="datatype-binary-sqlesc">.
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
</para>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<table id="datatype-binary-sqlesc">
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<title><acronym>SQL</acronym> Literal Escaped Octets</title>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<tgroup cols="5">
<thead>
<row>
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<entry>Decimal Octet Value</entry>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<entry>Description</entry>
<entry>Input Escaped Representation</entry>
<entry>Example</entry>
<entry>Printed Result</entry>
</row>
</thead>
<tbody>
<row>
<entry> <literal> 0 </literal> </entry>
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<entry> zero octet </entry>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<entry> <literal> '\\000' </literal> </entry>
<entry> <literal> select '\\000'::bytea; </literal> </entry>
<entry> <literal> \000 </literal></entry>
</row>
<row>
<entry> <literal> 39 </literal> </entry>
<entry> single quote </entry>
<entry> <literal> '\\'' or '\\047' </literal> </entry>
<entry> <literal> select '\''::bytea; </literal></entry>
<entry> <literal> ' </literal></entry>
</row>
<row>
<entry> <literal>92</literal> </entry>
<entry> backslash </entry>
<entry> <literal> '\\\\' or '\\134' </literal> </entry>
<entry> <literal> select '\\\\'::bytea; </literal></entry>
<entry> <literal> \\ </literal></entry>
</row>
</tbody>
</tgroup>
</table>
<para>
Note that the result in each of the examples above was exactly one
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
octet in length, even though the output representation of the zero
octet and backslash are more than one character. <type>Bytea</type>
output octets are also escaped. In general, each
<quote>non-printable</quote> octet decimal value is converted into
Spelling and grammatical corrections.
2001-11-21 22:12:34 +01:00
its equivalent three digit octal value, and preceded by one backslash.
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
Most <quote>printable</quote> octets are represented by their standard
representation in the client character set. The octet with decimal
value 92 (backslash) has a special alternate output representation.
Details are in <xref linkend="datatype-binary-resesc">.
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
</para>
<table id="datatype-binary-resesc">
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<title><acronym>SQL</acronym> Output Escaped Octets</title>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<tgroup cols="5">
<thead>
<row>
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<entry>Decimal Octet Value</entry>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<entry>Description</entry>
<entry>Output Escaped Representation</entry>
<entry>Example</entry>
<entry>Printed Result</entry>
</row>
</thead>
<tbody>
<row>
<entry> <literal> 92 </literal> </entry>
<entry> backslash </entry>
<entry> <literal> \\ </literal> </entry>
<entry> <literal> select '\\134'::bytea; </literal></entry>
<entry> <literal> \\ </literal></entry>
</row>
<row>
<entry> <literal> 0 to 31 and 127 to 255 </literal> </entry>
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<entry> <quote>non-printable</quote> octets </entry>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<entry> <literal> \### (octal value) </literal> </entry>
<entry> <literal> select '\\001'::bytea; </literal> </entry>
<entry> <literal> \001 </literal></entry>
</row>
<row>
<entry> <literal> 32 to 126 </literal> </entry>
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<entry> <quote>printable</quote> octets </entry>
Spelling and grammatical corrections.
2001-11-21 22:12:34 +01:00
<entry> ASCII representation </entry>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<entry> <literal> select '\\176'::bytea; </literal> </entry>
<entry> <literal> ~ </literal></entry>
</row>
</tbody>
</tgroup>
</table>
<para>
<acronym>SQL</acronym> string literals (input strings) must be
Spelling and grammatical corrections.
2001-11-21 22:12:34 +01:00
preceded with two backslashes due to the fact that they must pass
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
through two parsers in the PostgreSQL backend. The first backslash
proof-reading
2001-11-28 21:49:10 +01:00
is interpreted as an escape character by the string-literal parser,
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
and therefore is consumed, leaving the octets that follow.
Spelling and grammatical corrections.
2001-11-21 22:12:34 +01:00
The remaining backslash is recognized by the <type>bytea</type> input
function as the prefix of a three digit octal value. For example, a string
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
literal passed to the backend as <literal>'\\001'</literal> becomes
proof-reading
2001-11-28 21:49:10 +01:00
<literal>'\001'</literal> after passing through the string-literal
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
parser. The <literal>'\001'</literal> is then sent to the
<type>bytea</type> input function, where it is converted to a single
octet with a decimal value of 1.
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
</para>
<para>
For a similar reason, a backslash must be input as
<literal>'\\\\'</literal> (or <literal>'\\134'</literal>). The first
Spelling and grammatical corrections.
2001-11-21 22:12:34 +01:00
and third backslashes are interpreted as escape characters by the
proof-reading
2001-11-28 21:49:10 +01:00
string-literal parser, and therefore are consumed, leaving two
Spelling and grammatical corrections.
2001-11-21 22:12:34 +01:00
backslashes in the string passed to the <type>bytea</type> input function,
which interprets them as representing a single backslash.
For example, a string literal passed to the
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
backend as <literal>'\\\\'</literal> becomes <literal>'\\'</literal>
proof-reading
2001-11-28 21:49:10 +01:00
after passing through the string-literal parser. The
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<literal>'\\'</literal> is then sent to the <type>bytea</type> input
function, where it is converted to a single octet with a decimal
value of 92.
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
</para>
<para>
A single quote is a bit different in that it must be input as
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<literal>'\''</literal> (or <literal>'\\134'</literal>),
<emphasis>not</emphasis> as <literal>'\\''</literal>. This is because,
while the literal parser interprets the single quote as a special
character, and will consume the single backslash, the
<type>bytea</type> input function does <emphasis>not</emphasis>
recognize a single quote as a special octet. Therefore a string
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
literal passed to the backend as <literal>'\''</literal> becomes
proof-reading
2001-11-28 21:49:10 +01:00
<literal>'''</literal> after passing through the string-literal
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
parser. The <literal>'''</literal> is then sent to the
<type>bytea</type> input function, where it is retains its single
octet decimal value of 39.
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
</para>
<para>
Depending on the front end to PostgreSQL you use, you may have
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
additional work to do in terms of escaping and unescaping
<type>bytea</type> strings. For example, you may also have to escape
line feeds and carriage returns if your interface automatically
translates these. Or you may have to double up on backslashes if
the parser for your language or choice also treats them as an
Spelling and grammatical corrections.
2001-11-21 22:12:34 +01:00
escape character.
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
</para>
<sect2 id="datatype-binary-compat">
<title>Compatibility</title>
<para>
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<type>Bytea</type> provides most of the functionality of the binary
string type per SQL99 section 4.3. A comparison of SQL99 Binary
Strings and PostgreSQL <type>bytea</type> is presented in
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<xref linkend="datatype-binary-compat-comp">.
</para>
<table id="datatype-binary-compat-comp">
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<title>Comparison of SQL99 Binary String and PostgreSQL
<type>BYTEA</type> types</title>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
<tgroup cols="2">
<thead>
<row>
<entry>SQL99</entry>
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<entry><type>BYTEA</type></entry>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
</row>
</thead>
<tbody>
<row>
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
<entry> Name of data type <type>BINARY LARGE OBJECT</type>
or <type>BLOB</type> </entry>
<entry> Name of data type <type>BYTEA</type> </entry>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
</row>
<row>
<entry> Sequence of octets that does not have either a character set
or collation associated with it. </entry>
<entry> same </entry>
</row>
<row>
<entry> Described by a binary data type descriptor containing the
name of the data type and the maximum length
in octets</entry>
<entry> Described by a binary data type descriptor containing the
name of the data type with no specific maximum length
</entry>
</row>
<row>
<entry> All binary strings are mutually comparable in accordance
with the rules of comparison predicates.</entry>
<entry> same</entry>
</row>
<row>
<entry> Binary string values can only be compared for equality.
</entry>
<entry> Binary string values can be compared for equality, greater
than, greater than or equal, less than, less than or equal
</entry>
</row>
<row>
<entry> Operators operating on and returning binary strings
include concatenation, substring, overlay, and trim</entry>
<entry> Operators operating on and returning binary strings
proof-reading
2001-11-28 21:49:10 +01:00
include concatenation, substring, and trim. The
<literal>leading</literal> and <literal>trailing</literal>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
arguments for trim are not yet implemented.
</entry>
</row>
<row>
<entry> Other operators involving binary strings
include length, position, and the like predicate</entry>
<entry> same</entry>
</row>
<row>
<entry> A binary string literal is comprised of an even number of
Spelling and grammatical corrections.
2001-11-21 22:12:34 +01:00
hexadecimal digits, in single quotes, preceded by <quote>X</quote>,
Peter Eisentraut wrote: > So I would base this discussion on the premise "bytea stores binary data" > (insert examples). > > Some stylistic issues: > > bytea => <type>bytea</type> > > NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded) > > 'non-printable' => <quote>nonprintable</quote> > > MUST => <emphasis>must</emphasis> > Here's a patch against *CVS tip* to address Peter's comments. Please let me know what you think! Joe Conway
2001-11-21 04:17:22 +01:00
e.g. <literal>X'1a43fe'</literal></entry>
<entry> A binary string literal is comprised of octets
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
escaped according to the rules shown in
<xref linkend="datatype-binary-sqlesc"> </entry>
</row>
</tbody>
</tgroup>
</table>
</sect2>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
</sect1>
I've created a new section to func.sgml, "Binary String Functions and Operators", plagiarized shamelessly from the "String Functions and Operators" section. There were enough differences that it made sense (at least to me) to give this its own section instead of cramming it in with normal string functions. This way I could also make the examples relevant, which is particularly important for bytea. One thing I think worth mentioning: while documenting the trim() function I realized that I never implemented the bytea equivalent of rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim, available with text, are not available with bytea (I'd be happy to correct this, but since it would require an initdb, I guess not until 7.3) -- the submitted doc accurately reflects this. I will look for other areas of the docs that need mention of bytea, but any guidance would be much appreciated. -- Here's a second bytea documentation patch. This one significantly expands the "Binary Data" section added by Bruce recently. Joe Conway
2001-11-20 16:42:44 +01:00
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect1 id="datatype-datetime">
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
<title>Date/Time Types</title>
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</productname> supports the full set of
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<acronym>SQL</acronym> date and time types.
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
</para>
Include new cidr and inet data types.
1998-10-27 07:14:41 +01:00
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
<para>
<table tocentry="1">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Date/Time Types</title>
Bunch of copy fitting and style sheet tweakage to get decent looking print output (from pdfjadetex). Also updated instructions to install documentation processing toolchain.
2001-10-09 20:46:00 +02:00
<tgroup cols="6">
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
<thead>
<row>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>Type</entry>
<entry>Description</entry>
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
<entry>Storage</entry>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>Earliest</entry>
<entry>Latest</entry>
<entry>Resolution</entry>
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
</row>
</thead>
<tbody>
<row>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<entry><type>timestamp [ (<replaceable>p</replaceable>) ] without time zone</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>both date and time</entry>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>8 bytes</entry>
<entry>4713 BC</entry>
<entry>AD 1465001</entry>
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<entry>1 microsecond / 14 digits</entry>
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
</row>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<row>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<entry><type>timestamp [ (<replaceable>p</replaceable>) ] [ with time zone ]</type></entry>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
<entry>both date and time</entry>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<entry>8 bytes</entry>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
<entry>4713 BC</entry>
<entry>AD 1465001</entry>
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<entry>1 microsecond / 14 digits</entry>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
</row>
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
<row>
Type interval takes a precision, too.
2001-12-23 21:21:37 +01:00
<entry><type>interval [ (<replaceable>p</replaceable>) ]</type></entry>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>for time intervals</entry>
<entry>12 bytes</entry>
<entry>-178000000 years</entry>
<entry>178000000 years</entry>
Fix several <ulink> tags which refer to e-mail addresses but were missing the "mailto:" prefix. Fix typo. Thanks to Neil Conway <nconway@klamath.dyndns.org> for the heads-up.
2000-08-23 07:59:11 +02:00
<entry>1 microsecond</entry>
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
</row>
<row>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry><type>date</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>dates only</entry>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>4 bytes</entry>
<entry>4713 BC</entry>
<entry>32767 AD</entry>
<entry>1 day</entry>
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
</row>
<row>
Document the precision arguments for date/time types per SQL9x. Update the list of recognized time zones. Document the range of arguments allowed for SET TIME ZONE. Still need to add info on other date/time symbols (e.g. "AM", "T") and to freshen the docs on the date/time parsing rules.
2001-12-29 19:35:54 +01:00
<entry><type>time [ (<replaceable>p</replaceable>) ] [ without time zone ]</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>times of day only</entry>
Since 7.1 the data type size of TIME has been increased.
2001-08-31 03:55:25 +02:00
<entry>8 bytes</entry>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>00:00:00.00</entry>
<entry>23:59:59.99</entry>
<entry>1 microsecond</entry>
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
</row>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<row>
Document the precision arguments for date/time types per SQL9x. Update the list of recognized time zones. Document the range of arguments allowed for SET TIME ZONE. Still need to add info on other date/time symbols (e.g. "AM", "T") and to freshen the docs on the date/time parsing rules.
2001-12-29 19:35:54 +01:00
<entry><type>time [ (<replaceable>p</replaceable>) ] with time zone</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>times of day only</entry>
Since 7.1 the data type size of TIME has been increased.
2001-08-31 03:55:25 +02:00
<entry>12 bytes</entry>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<entry>00:00:00.00+12</entry>
<entry>23:59:59.99-12</entry>
<entry>1 microsecond</entry>
</row>
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
</tbody>
</tgroup>
</table>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
</para>
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<para>
Type interval takes a precision, too.
2001-12-23 21:21:37 +01:00
<type>time</type>, <type>timestamp</type>, and <type>interval</type>
accept an
optional precision value <replaceable>p</replaceable> which
specifies the number of fractional digits retained in the seconds
field. By default, there is no explicit bound on precision. The
effective limit of precision is determined by the underlying double
precision floating point number used to store values (in seconds
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
for <type>interval</type> and
Type interval takes a precision, too.
2001-12-23 21:21:37 +01:00
in seconds since 2000-01-01 for <type>timestamp</type>). The
useful range of <replaceable>p</replaceable> is from 0 to about
6 for <type>timestamp</type>, but may be more for <type>interval</type>.
The system will accept <replaceable>p</replaceable> ranging from
0 to 13.
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
</para>
<para>
Time zones, and time-zone conventions, are influenced by
Add more complete details on date/time keywords and parsing rules. Move some tabular information on these from the chapter on data types to the appendix on dates and times.
2002-01-04 18:02:25 +01:00
political decisions, not just earth geometry. Time zones around the
Spiff up discussion of precision on date/time data types. Add a NetBSD/alpha and update info on a few other platforms.
2001-12-21 04:54:02 +01:00
world became somewhat standardized during the 1900's,
but continue to be prone to arbitrary changes.
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<productname>PostgreSQL</productname> uses your operating
Add more complete details on date/time keywords and parsing rules. Move some tabular information on these from the chapter on data types to the appendix on dates and times.
2002-01-04 18:02:25 +01:00
system's underlying features to provide output time-zone
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
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).
Add more complete details on date/time keywords and parsing rules. Move some tabular information on these from the chapter on data types to the appendix on dates and times.
2002-01-04 18:02:25 +01:00
<type>timestamp with time zone</type> and <type>time with time
zone</type> will use time zone
information only within that year range, and assume that times
outside that range are in <acronym>UTC</acronym>.
Include specific info on available timezones. Document date/time input parsing procedure.
1999-05-04 04:22:13 +02:00
</para>
Include new cidr and inet data types.
1998-10-27 07:14:41 +01:00
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
<para>
Add more complete details on date/time keywords and parsing rules. Move some tabular information on these from the chapter on data types to the appendix on dates and times.
2002-01-04 18:02:25 +01:00
To ensure an upgrade path from versions of
<productname>PostgreSQL</productname> earlier than 7.0,
we recognize <type>datetime</type>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
(equivalent to <type>timestamp</type>) and
Add more complete details on date/time keywords and parsing rules. Move some tabular information on these from the chapter on data types to the appendix on dates and times.
2002-01-04 18:02:25 +01:00
<type>timespan</type> (equivalent to <type>interval</type>).
These types are
now restricted to having an
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
implicit translation to <type>timestamp</type> and
Add more complete details on date/time keywords and parsing rules. Move some tabular information on these from the chapter on data types to the appendix on dates and times.
2002-01-04 18:02:25 +01:00
<type>interval</type>, and
support for these will be removed in the next release of
<productname>PostgreSQL</productname> (likely named 7.3).
</para>
<para>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
The types <type>abstime</type>
and <type>reltime</type> are lower precision types which are used internally.
You are discouraged from using any of these types in new
applications and are encouraged to move any old
ones over when appropriate. Any or all of these internal types
might disappear in a future release.
</para>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect2 id="datatype-datetime-input">
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
<title>Date/Time Input</title>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
<para>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
Date and time input is accepted in almost any reasonable format, including
proof-reading
2001-11-28 21:49:10 +01:00
<acronym>ISO 8601</acronym>, <acronym>SQL</acronym>-compatible,
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
traditional <productname>PostgreSQL</productname>, and others.
Spiff up discussion of precision on date/time data types. Add a NetBSD/alpha and update info on a few other platforms.
2001-12-21 04:54:02 +01:00
For some formats, ordering of month and day in date input can be
ambiguous and there is support for specifying the expected
ordering of these fields.
The command
<literal>SET DateStyle TO 'US'</literal>
or <literal>SET DateStyle TO 'NonEuropean'</literal>
Replace ASCII-quotes with proper markup.
2001-09-13 17:55:24 +02:00
specifies the variant <quote>month before day</quote>, the command
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<literal>SET DateStyle TO 'European'</literal> sets the variant
Replace ASCII-quotes with proper markup.
2001-09-13 17:55:24 +02:00
<quote>day before month</quote>. The <literal>ISO</literal> style
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
is the default but this default can be changed at compile time or at run time.
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
</para>
<para>
Spiff up discussion of precision on date/time data types. Add a NetBSD/alpha and update info on a few other platforms.
2001-12-21 04:54:02 +01:00
<productname>PostgreSQL</productname> is more flexible in
handling date/time than the
<acronym>SQL</acronym> standard requires.
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
See <xref linkend="datetime-appendix">
Spiff up discussion of precision on date/time data types. Add a NetBSD/alpha and update info on a few other platforms.
2001-12-21 04:54:02 +01:00
for the exact parsing rules of date/time input and for the
Add more complete details on date/time keywords and parsing rules. Move some tabular information on these from the chapter on data types to the appendix on dates and times.
2002-01-04 18:02:25 +01:00
recognized text fields including months, days of the week, and
time zones.
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</para>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
<para>
Spiff up discussion of precision on date/time data types. Add a NetBSD/alpha and update info on a few other platforms.
2001-12-21 04:54:02 +01:00
Remember that any date or time literal input needs to be enclosed
in single quotes, like text strings. Refer to
<xref linkend="sql-syntax-constants-generic"> for more
information.
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<acronym>SQL9x</acronym> requires the following syntax
Add some links from data type chapter to section on literal constants.
2001-01-26 23:04:22 +01:00
<synopsis>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<replaceable>type</replaceable> [ (<replaceable>p</replaceable>) ] '<replaceable>value</replaceable>'
Add some links from data type chapter to section on literal constants.
2001-01-26 23:04:22 +01:00
</synopsis>
Spiff up discussion of precision on date/time data types. Add a NetBSD/alpha and update info on a few other platforms.
2001-12-21 04:54:02 +01:00
where <replaceable>p</replaceable> in the optional precision
specification is an integer corresponding to the
number of fractional digits in the seconds field. Precision can
be specified
for <type>time</type>, <type>timestamp</type>, and
<type>interval</type> types.
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</para>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<sect3>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<title><type>date</type></title>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>date</primary>
<secondary>data type</secondary>
</indexterm>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
<para>
Add more complete details on date/time keywords and parsing rules. Move some tabular information on these from the chapter on data types to the appendix on dates and times.
2002-01-04 18:02:25 +01:00
The following are some possible inputs for the <type>date</type> type.
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
<table tocentry="1">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Date Input</title>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
<tgroup cols="2">
<thead>
<row>
<entry>Example</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>January 8, 1999</entry>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>Unambiguous</entry>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</row>
<row>
<entry>1999-01-08</entry>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>ISO-8601 format, preferred</entry>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</row>
<row>
<entry>1/8/1999</entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>U.S.; read as August 1 in European mode</entry>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</row>
<row>
<entry>8/1/1999</entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>European; read as August 1 in U.S. mode</entry>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</row>
<row>
<entry>1/18/1999</entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>U.S.; read as January 18 in any mode</entry>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</row>
<row>
<entry>19990108</entry>
<entry>ISO-8601 year, month, day</entry>
</row>
<row>
<entry>990108</entry>
<entry>ISO-8601 year, month, day</entry>
</row>
<row>
<entry>1999.008</entry>
<entry>Year and day of year</entry>
</row>
<row>
<entry>99008</entry>
<entry>Year and day of year</entry>
</row>
<row>
Add more complete details on date/time keywords and parsing rules. Move some tabular information on these from the chapter on data types to the appendix on dates and times.
2002-01-04 18:02:25 +01:00
<entry>J2451187</entry>
<entry>Julian day</entry>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</row>
<row>
Add more complete details on date/time keywords and parsing rules. Move some tabular information on these from the chapter on data types to the appendix on dates and times.
2002-01-04 18:02:25 +01:00
<entry>January 8, 99 BC</entry>
<entry>Year 99 before the Common Era</entry>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</row>
</tbody>
</tgroup>
</table>
</para>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</sect3>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<sect3>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<title><type>time [ ( <replaceable>p</replaceable> ) ] [ without time zone ]</type></title>
Update docs for TIME WITHOUT TIME ZONE. Add information on SET SESSION CHARACTERISTICS. Fix references to pg_hba.conf(5) since that is no longer a man page.
2000-07-14 17:26:21 +02:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>time</primary>
<secondary>data type</secondary>
</indexterm>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
<indexterm>
<primary>time without time zone</primary>
<secondary>time</secondary>
</indexterm>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
Update docs for TIME WITHOUT TIME ZONE. Add information on SET SESSION CHARACTERISTICS. Fix references to pg_hba.conf(5) since that is no longer a man page.
2000-07-14 17:26:21 +02:00
<para>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
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.
Update docs for TIME WITHOUT TIME ZONE. Add information on SET SESSION CHARACTERISTICS. Fix references to pg_hba.conf(5) since that is no longer a man page.
2000-07-14 17:26:21 +02:00
</para>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<para>
The following are valid <type>time</type> inputs.
<table tocentry="1">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Time Input</title>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<tgroup cols="2">
<thead>
<row>
<entry>Example</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>04:05:06.789</entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>ISO 8601</entry>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
</row>
<row>
<entry>04:05:06</entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>ISO 8601</entry>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
</row>
<row>
<entry>04:05</entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>ISO 8601</entry>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
</row>
<row>
<entry>040506</entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>ISO 8601</entry>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
</row>
<row>
<entry>04:05 AM</entry>
<entry>Same as 04:05; AM does not affect value</entry>
</row>
<row>
<entry>04:05 PM</entry>
<entry>Same as 16:05; input hour must be <= 12</entry>
</row>
<row>
<entry>allballs</entry>
<entry>Same as 00:00:00</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</sect3>
<sect3>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<title><type>time [ ( <replaceable>precision</replaceable> ) ] with time zone</type></title>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
<indexterm>
<primary>time with time zone</primary>
<secondary>data type</secondary>
</indexterm>
<indexterm>
<primary>time</primary>
<secondary>data type</secondary>
</indexterm>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<para>
This type is defined by SQL92, but the definition exhibits
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
properties which lead to questionable usefulness. In
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
most cases, a combination of <type>date</type>,
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
<type>time</type>, <type>timestamp without time zone</type>
and <type>timestamp with time zone</type>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
should provide a complete range of date/time functionality
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
required by any application.
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
</para>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<para>
The optional precision
<replaceable>p</replaceable> should be between 0 and 13, and
defaults to the precision of the input time literal.
</para>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<para>
<type>time with time zone</type> accepts all input also legal
for the <type>time</type> type, appended with a legal time zone,
as follows:
<table tocentry="1">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Time With Time Zone Input</title>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<tgroup cols="2">
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
<thead>
<row>
<entry>Example</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<entry>04:05:06.789-8</entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>ISO 8601</entry>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</row>
<row>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<entry>04:05:06-08:00</entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>ISO 8601</entry>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</row>
<row>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<entry>04:05-08:00</entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>ISO 8601</entry>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</row>
<row>
Updated user's guide to match new psql's output format Fixed bug in createdb/alternative location
2000-03-26 20:32:30 +02:00
<entry>040506-08</entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>ISO 8601</entry>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
</row>
</tbody>
</tgroup>
</table>
</para>
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
<para>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
Refer to <xref linkend="datatype-timezone-table"> for
Write up new TIME WITH TIME ZONE type.
2000-03-14 23:52:53 +01:00
more examples of time zones.
</para>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</sect3>
<sect3>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<title><type>timestamp [ (<replaceable>precision</replaceable>) ] without time zone</type></title>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
<indexterm>
<primary>timestamp without time zone</primary>
<secondary>data type</secondary>
</indexterm>
<para>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
Valid input for the <type>timestamp [ (<replaceable>p</replaceable>) ] without time zone</type>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
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.)
Thus
Spacing improvements
2001-11-09 00:36:55 +01:00
<programlisting>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
1999-01-08 04:05:06
Spacing improvements
2001-11-09 00:36:55 +01:00
</programlisting>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
is a valid <type>timestamp without time zone</type> value that
is <acronym>ISO</acronym>-compliant.
In addition, the wide-spread format
Spacing improvements
2001-11-09 00:36:55 +01:00
<programlisting>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
January 8 04:05:06 1999 PST
Spacing improvements
2001-11-09 00:36:55 +01:00
</programlisting>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
is supported.
</para>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<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>
Add information on new timestamp and timestamptz data types. Start chapter on recovery techniques. Still needs work for release.
2001-09-28 10:15:35 +02:00
<para>
For <type>timestamp without time zone</type>, any explicit time
zone specified in the input is silently swallowed. That is, the
resulting date/time value is derived from the explicit date/time
fields in the input value, and is not adjusted for time zone.
</para>
</sect3>
<sect3>
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<title><type>timestamp [ (<replaceable>precision</replaceable>) ] with time zone</type></title>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>timestamp</primary>
<secondary>data type</secondary>
</indexterm>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<para>
Valid input for the <type>timestamp</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.)
Thus
Spacing improvements
2001-11-09 00:36:55 +01:00
<programlisting>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
1999-01-08 04:05:06 -8:00
Spacing improvements
2001-11-09 00:36:55 +01:00
</programlisting>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
Replace incorrect uses of 'which' with 'that'. (so-called "wicked which")
2000-12-22 19:57:50 +01:00
is a valid <type>timestamp</type> value that is <acronym>ISO</acronym>-compliant.
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
In addition, the wide-spread format
Spacing improvements
2001-11-09 00:36:55 +01:00
<programlisting>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
January 8 04:05:06 1999 PST
Spacing improvements
2001-11-09 00:36:55 +01:00
</programlisting>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
is supported.
</para>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<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>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<para>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<table tocentry="1" id="datatype-timezone-table">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Time Zone Input</title>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<tgroup cols="2">
<thead>
<row>
<entry>Time Zone</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>PST</entry>
<entry>Pacific Standard Time</entry>
</row>
<row>
<entry>-8:00</entry>
<entry>ISO-8601 offset for PST</entry>
</row>
<row>
<entry>-800</entry>
<entry>ISO-8601 offset for PST</entry>
</row>
<row>
<entry>-8</entry>
<entry>ISO-8601 offset for PST</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</sect3>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<sect3>
Type interval takes a precision, too.
2001-12-23 21:21:37 +01:00
<title><type>interval [ ( <replaceable>precision</replaceable> ) ]</type></title>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>interval</primary>
</indexterm>
Add tables of allowed values and formats for date/time input types. Include info for time zones, days of week, months. Procedural description of date input parsing is not yet complete.
1999-01-19 17:08:26 +01:00
<para>
A bunch of small doco updates motivated by scanning the comments on the interactive docs.
2001-11-19 04:58:25 +01:00
<type>interval</type> values can be written with the following syntax:
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
Spacing improvements
2001-11-09 00:36:55 +01:00
<programlisting>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
Quantity Unit [Quantity Unit...] [Direction]
A bunch of small doco updates motivated by scanning the comments on the interactive docs.
2001-11-19 04:58:25 +01:00
@ Quantity Unit [Quantity Unit...] [Direction]
Spacing improvements
2001-11-09 00:36:55 +01:00
</programlisting>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
Type interval takes a precision, too.
2001-12-23 21:21:37 +01:00
where: <literal>Quantity</literal> is a number (possibly signed),
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<literal>Unit</literal> is <literal>second</literal>,
<literal>minute</literal>, <literal>hour</literal>, <literal>day</literal>,
<literal>week</literal>, <literal>month</literal>, <literal>year</literal>,
<literal>decade</literal>, <literal>century</literal>, <literal>millennium</literal>,
or abbreviations or plurals of these units;
<literal>Direction</literal> can be <literal>ago</literal> or
A bunch of small doco updates motivated by scanning the comments on the interactive docs.
2001-11-19 04:58:25 +01:00
empty. The at sign (<literal>@</>) is optional noise. The amounts
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
of different units are implicitly added up with appropriate
A bunch of small doco updates motivated by scanning the comments on the interactive docs.
2001-11-19 04:58:25 +01:00
sign accounting.
</para>
<para>
Quantities of days, hours, minutes, and seconds can be specified without
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
explicit unit markings. For example, <literal>'1 12:59:10'</> is read
A bunch of small doco updates motivated by scanning the comments on the interactive docs.
2001-11-19 04:58:25 +01:00
the same as <literal>'1 day 12 hours 59 min 10 sec'</>.
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
</para>
Type interval takes a precision, too.
2001-12-23 21:21:37 +01:00
<para>
The optional precision
<replaceable>p</replaceable> should be between 0 and 13, and
defaults to the precision of the input literal.
</para>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
</sect3>
Describe the date/time parsing rules. Include specific information on the supported time zones. It's a really big table, so maybe it should go into an appendix instead.
1999-02-13 04:42:10 +01:00
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<sect3>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<title>Special values</title>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>time</primary>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<secondary>constants</secondary>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
</indexterm>
<indexterm>
<primary>date</primary>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<secondary>constants</secondary>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
</indexterm>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
The following <acronym>SQL</acronym>-compatible functions can be
used as date or time
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
input for the corresponding data type: <literal>CURRENT_DATE</literal>,
Update list of currently supported platforms. Mention SQL9x precision syntax for date/time types. Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:23 +01:00
<literal>CURRENT_TIME</literal>,
<literal>CURRENT_TIMESTAMP</literal>. The latter two accept an
optional precision specification.
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
</para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</productname> also supports several
special constants for convenience.
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<table tocentry="1">
<title>Special Date/Time Constants</title>
<tgroup cols="2">
<thead>
<row>
<entry>Constant</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>epoch</entry>
<entry>1970-01-01 00:00:00+00 (Unix system time zero)</entry>
</row>
<row>
<entry>infinity</entry>
<entry>Later than other valid times</entry>
</row>
<row>
<entry>-infinity</entry>
<entry>Earlier than other valid times</entry>
</row>
<row>
<entry>invalid</entry>
<entry>Illegal entry</entry>
</row>
<row>
<entry>now</entry>
<entry>Current transaction time</entry>
</row>
<row>
<entry>today</entry>
<entry>Midnight today</entry>
</row>
<row>
<entry>tomorrow</entry>
<entry>Midnight tomorrow</entry>
</row>
<row>
<entry>yesterday</entry>
<entry>Midnight yesterday</entry>
</row>
<row>
<entry>zulu, allballs, z</entry>
<entry>00:00:00.00 GMT</entry>
</row>
</tbody>
</tgroup>
</table>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<literal>'now'</literal> is
evaluated when the value is first interpreted.
proof-reading
2001-11-28 21:49:10 +01:00
</para>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
proof-reading
2001-11-28 21:49:10 +01:00
<note>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<para>
As of <productname>PostgreSQL</> version 7.2,
<literal>'current'</literal> is no longer supported as a
date/time constant.
Previously,
<literal>'current'</literal> was stored as a special value,
and evaluated to <literal>'now'</literal> only when
proof-reading
2001-11-28 21:49:10 +01:00
used in an expression or type
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
conversion.
</para>
proof-reading
2001-11-28 21:49:10 +01:00
</note>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
</sect3>
</sect2>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect2 id="datatype-datetime-output">
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<title>Date/Time Output</title>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>date</primary>
<secondary>output format</secondary>
<seealso>Formatting</seealso>
</indexterm>
<indexterm>
<primary>time</primary>
<secondary>output format</secondary>
<seealso>Formatting</seealso>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
Output formats can be set to one of the four styles
proof-reading
2001-11-28 21:49:10 +01:00
ISO 8601, <acronym>SQL</acronym> (Ingres), traditional
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
PostgreSQL, and German, using the <command>SET DateStyle</command>.
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
The default is the <acronym>ISO</acronym> format.
<table tocentry="1">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Date/Time Output Styles</title>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<tgroup cols="3">
<thead>
<row>
<entry>Style Specification</entry>
<entry>Description</entry>
<entry>Example</entry>
</row>
</thead>
<tbody>
<row>
<entry>'ISO'</entry>
<entry>ISO-8601 standard</entry>
<entry>1997-12-17 07:37:16-08</entry>
</row>
<row>
<entry>'SQL'</entry>
<entry>Traditional style</entry>
<entry>12/17/1997 07:37:16.00 PST</entry>
</row>
<row>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<entry>'PostgreSQL'</entry>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>Original style</entry>
<entry>Wed Dec 17 07:37:16 1997 PST</entry>
</row>
<row>
<entry>'German'</entry>
<entry>Regional style</entry>
<entry>17.12.1997 07:37:16.00 PST</entry>
</row>
</tbody>
</tgroup>
</table>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
The output of the <type>date</type> and <type>time</type> styles
is of course
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
only the date or time part in accordance with the above examples.
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
</para>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
The <acronym>SQL</acronym> style has European and non-European
proof-reading
2001-11-28 21:49:10 +01:00
(U.S.) variants,
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
which determines whether month follows day or vice versa. (See
also <xref linkend="datatype-datetime-input">
for how this setting affects interpretation of
input values.)
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<table tocentry="1">
proof-reading
2001-11-28 21:49:10 +01:00
<title>Date-Order Conventions</title>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<tgroup cols="3">
<thead>
<row>
<entry>Style Specification</entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>Description</entry>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>Example</entry>
</row>
</thead>
<tbody>
<row>
<entry>European</entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry><replaceable>day</replaceable>/<replaceable>month</replaceable>/<replaceable>year</replaceable></entry>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>17/12/1997 15:37:16.00 MET</entry>
</row>
<row>
<entry>US</entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry><replaceable>month</replaceable>/<replaceable>day</replaceable>/<replaceable>year</replaceable></entry>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<entry>12/17/1997 07:37:16.00 PST</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<type>interval</type> output looks like the input format, except that units like
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<literal>week</literal> or <literal>century</literal> are converted to years and days.
In ISO mode the output looks like
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<programlisting>
[ Quantity Units [ ... ] ] [ Days ] Hours:Minutes [ ago ]
</programlisting>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
<para>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
There are several ways to affect the appearance of date/time types:
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<itemizedlist spacing="compact" mark="bullet">
<listitem>
<para>
The <envar>PGDATESTYLE</envar> environment variable used by the backend directly
Startup is actually start-up.
2000-08-29 22:02:09 +02:00
on postmaster start-up.
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</para>
</listitem>
<listitem>
<para>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
The <envar>PGDATESTYLE</envar> environment variable used by the frontend <application>libpq</application>
Startup is actually start-up.
2000-08-29 22:02:09 +02:00
on session start-up.
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</para>
</listitem>
<listitem>
<para>
<command>SET DATESTYLE</command> <acronym>SQL</acronym> command.
</para>
</listitem>
</itemizedlist>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</sect2>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect2 id="datatype-timezones">
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<title>Time Zones</title>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm zone="datatype-timezones">
<primary>time zones</primary>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</productname> endeavors to be compatible with
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<acronym>SQL92</acronym> definitions for typical usage.
However, the <acronym>SQL92</acronym> standard has an odd mix of date and
time types and capabilities. Two obvious problems are:
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<itemizedlist>
<listitem>
<para>
Although the <type>date</type> type
does not have an associated time zone, the
Grammatical and spelling fixes.
2001-11-19 10:05:02 +01:00
<type>time</type> type can.
Mention new AT TIME ZONE feature.
2000-11-11 20:50:31 +01:00
Time zones in the real world can have no meaning unless
associated with a date as well as a time
proof-reading
2001-11-28 21:49:10 +01:00
since the offset may vary through the year with daylight-saving
Mention new AT TIME ZONE feature.
2000-11-11 20:50:31 +01:00
time boundaries.
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</para>
</listitem>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<listitem>
<para>
The default time zone is specified as a constant integer offset
proof-reading
2001-11-28 21:49:10 +01:00
from GMT/UTC. It is not possible to adapt to daylight-saving
Mention new AT TIME ZONE feature.
2000-11-11 20:50:31 +01:00
time when doing date/time arithmetic across
<acronym>DST</acronym> boundaries.
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</para>
</listitem>
Add mention of the SERIAL data type. Change claim of "no limit" on maximum date for datetime type to more realistic 1465001 AD. Thanks Tatsuo for pointing this out :) Clean up markup.
1998-10-14 18:26:31 +02:00
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</itemizedlist>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<para>
Mention new AT TIME ZONE feature.
2000-11-11 20:50:31 +01:00
To address these difficulties, we recommend using date/time
Replace incorrect uses of 'which' with 'that'. (so-called "wicked which")
2000-12-22 19:57:50 +01:00
types that contain both date and time when using time zones. We
proof-reading
2001-11-28 21:49:10 +01:00
recommend <emphasis>not</emphasis> using the SQL92 type <type>time
with time zone</type> (though it is supported by
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</productname> for legacy applications and
Mention new AT TIME ZONE feature.
2000-11-11 20:50:31 +01:00
for compatibility with other RDBMS implementations).
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</productname>
Document the precision arguments for date/time types per SQL9x. Update the list of recognized time zones. Document the range of arguments allowed for SET TIME ZONE. Still need to add info on other date/time symbols (e.g. "AM", "T") and to freshen the docs on the date/time parsing rules.
2001-12-29 19:35:54 +01:00
assumes your local time zone for any type containing only
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
date or time. Further, time zone support is derived from
the underlying operating system
proof-reading
2001-11-28 21:49:10 +01:00
time-zone capabilities, and hence can handle daylight-saving time
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
and other expected behavior.
</para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
proof-reading
2001-11-28 21:49:10 +01:00
<productname>PostgreSQL</productname> obtains time-zone support
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
from the underlying operating system for dates between 1902 and
2038 (near the typical date limits for Unix-style
systems). Outside of this range, all dates are assumed to be
specified and used in Universal Coordinated Time (UTC).
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
<para>
Mention new AT TIME ZONE feature.
2000-11-11 20:50:31 +01:00
All dates and times are stored internally in UTC,
traditionally known as Greenwich Mean Time (GMT).
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
Times are converted to local time on the database server before being
sent to the client frontend, hence by default are in the server
time zone.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<para>
proof-reading
2001-11-28 21:49:10 +01:00
There are several ways to affect the time-zone behavior:
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<itemizedlist spacing="compact" mark="bullet">
<listitem>
<para>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
The <envar>TZ</envar> environment variable is used by the backend directly
Startup is actually start-up.
2000-08-29 22:02:09 +02:00
on postmaster start-up as the default time zone.
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</para>
</listitem>
<listitem>
<para>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
The <envar>PGTZ</envar> environment variable, if set at the client, is used by libpq
Fix some references to USE_AUSTRALIAN_RULES that Bruce missed; plus a few trivial improvements in wording.
2001-06-18 21:05:11 +02:00
to send a <command>SET TIME ZONE</command> command to the backend upon
connection.
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</para>
</listitem>
<listitem>
<para>
The <acronym>SQL</acronym> command <command>SET TIME ZONE</command>
sets the time zone for the session.
</para>
</listitem>
Mention new AT TIME ZONE feature.
2000-11-11 20:50:31 +01:00
<listitem>
<para>
The <acronym>SQL92</acronym> qualifier on
Spacing improvements
2001-11-09 00:36:55 +01:00
<programlisting>
Mention new AT TIME ZONE feature.
2000-11-11 20:50:31 +01:00
<replaceable>timestamp</replaceable> AT TIME ZONE '<replaceable>zone</replaceable>'
Spacing improvements
2001-11-09 00:36:55 +01:00
</programlisting>
Mention new AT TIME ZONE feature.
2000-11-11 20:50:31 +01:00
where <replaceable>zone</replaceable> can be specified as a
text time zone (e.g. <literal>'PST'</literal>) or as an
interval (e.g. <literal>INTERVAL '-08:00'</literal>).
</para>
</listitem>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</itemizedlist>
</para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Mention new AT TIME ZONE feature.
2000-11-11 20:50:31 +01:00
<note>
<para>
If an invalid time zone is specified,
the time zone becomes GMT (on most systems anyway).
</para>
</note>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<note>
<para>
Fix some references to USE_AUSTRALIAN_RULES that Bruce missed; plus a few trivial improvements in wording.
2001-06-18 21:05:11 +02:00
If the runtime option <literal>AUSTRALIAN_TIMEZONES</literal> is set
then <literal>CST</literal> and <literal>EST</literal> refer to
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
Australian time zones, not American ones.
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
</para>
</note>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</sect2>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect2 id="datatype-datetime-internals">
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
<title>Internals</title>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</productname> uses Julian dates
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
for all date/time calculations. They have the nice property of correctly
predicting/calculating any date more recent than 4713BC
to far into the future, using the assumption that the length of the
year is 365.2425 days.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
<para>
updated install file updated date/time types doc fixed small psql bug removed libpq code that lower-cased db names make notice when long identifier is truncated
2000-01-23 02:27:39 +01:00
Date conventions before the 19th century make for interesting reading,
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
but are not consistent enough to warrant coding into a date/time handler.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
</sect2>
</sect1>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect1 id="datatype-boolean">
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<title>Boolean Type</title>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm zone="datatype-boolean">
<primary>Boolean</primary>
<secondary>data type</secondary>
</indexterm>
<indexterm zone="datatype-boolean">
<primary>true</primary>
</indexterm>
<indexterm zone="datatype-boolean">
<primary>false</primary>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</productname> provides the
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<acronym>SQL99</acronym> type <type>boolean</type>.
<type>boolean</type> can have one of only two states:
<quote>true</quote> or <quote>false</quote>. A third state,
<quote>unknown</quote>, is represented by the
<acronym>SQL</acronym> NULL state.
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
</para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
Valid literal values for the <quote>true</quote> state are:
<simplelist>
<member><literal>TRUE</literal></member>
<member><literal>'t'</literal></member>
<member><literal>'true'</literal></member>
<member><literal>'y'</literal></member>
<member><literal>'yes'</literal></member>
<member><literal>'1'</literal></member>
</simplelist>
For the <quote>false</quote> state, the following values can be
used:
<simplelist>
<member><literal>FALSE</literal></member>
<member><literal>'f'</literal></member>
<member><literal>'false'</literal></member>
<member><literal>'n'</literal></member>
<member><literal>'no'</literal></member>
<member><literal>'0'</literal></member>
</simplelist>
Using the key words <literal>TRUE</literal> and
<literal>FALSE</literal> is preferred (and
<acronym>SQL</acronym>-compliant).
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<example id="datatype-boolean-example">
<title>Using the <type>boolean</type> type</title>
<programlisting>
CREATE TABLE test1 (a boolean, b text);
INSERT INTO test1 VALUES (TRUE, 'sic est');
INSERT INTO test1 VALUES (FALSE, 'non est');
SELECT * FROM test1;
a | b
---+---------
t | sic est
f | non est
SELECT * FROM test1 WHERE a;
a | b
---+---------
t | sic est
</programlisting>
</example>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<xref linkend="datatype-boolean-example"> shows that
<type>boolean</type> values are output using the letters
<literal>t</literal> and <literal>f</literal>.
</para>
<tip>
<para>
Values of the <type>boolean</type> type cannot be cast directly
to other types (e.g., <literal>CAST
(<replaceable>boolval</replaceable> AS integer)</literal> does
not work). This can be accomplished using the
<literal>CASE</literal> expression: <literal>CASE WHEN
<replaceable>boolval</replaceable> THEN 'value if true' ELSE
'value if false' END</literal>. See also <xref
linkend="functions-conditional">.
</para>
</tip>
<para>
<type>boolean</type> uses 1 byte of storage.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
</sect1>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect1 id="datatype-geometric">
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<title>Geometric Types</title>
<para>
Geometric types represent two-dimensional spatial objects.
The most fundamental type,
the point, forms the basis for all of the other types.
</para>
<para>
<table tocentry="1">
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
<title>Geometric Types</title>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<tgroup cols="4">
<thead>
<row>
<entry>Geometric Type</entry>
<entry>Storage</entry>
<entry>Representation</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>point</type></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>16 bytes</entry>
<entry>(x,y)</entry>
<entry>Point in space</entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>line</type></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>32 bytes</entry>
<entry>((x1,y1),(x2,y2))</entry>
<entry>Infinite line</entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>lseg</type></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>32 bytes</entry>
<entry>((x1,y1),(x2,y2))</entry>
<entry>Finite line segment</entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>box</type></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>32 bytes</entry>
<entry>((x1,y1),(x2,y2))</entry>
<entry>Rectangular box</entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>path</type></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>4+32n bytes</entry>
<entry>((x1,y1),...)</entry>
<entry>Closed path (similar to polygon)</entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>path</type></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>4+32n bytes</entry>
<entry>[(x1,y1),...]</entry>
<entry>Open path</entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>polygon</type></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>4+32n bytes</entry>
<entry>((x1,y1),...)</entry>
<entry>Polygon (similar to closed path)</entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>circle</type></entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>24 bytes</entry>
<entry><(x,y),r></entry>
<entry>Circle (center and radius)</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
<para>
A rich set of functions and operators is available to perform various geometric
operations such as scaling, translation, rotation, and determining
intersections.
</para>
<sect2>
<title>Point</title>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>point</primary>
</indexterm>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<para>
Points are the fundamental two-dimensional building block for geometric types.
</para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
<type>point</type> is specified using the following syntax:
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<synopsis>
( <replaceable>x</replaceable> , <replaceable>y</replaceable> )
<replaceable>x</replaceable> , <replaceable>y</replaceable>
</synopsis>
where the arguments are
<variablelist>
<varlistentry>
<term><replaceable>x</replaceable></term>
<listitem>
<para>
proof-reading
2001-11-28 21:49:10 +01:00
The x-axis coordinate as a floating-point number
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><replaceable>y</replaceable></term>
<listitem>
<para>
proof-reading
2001-11-28 21:49:10 +01:00
The y-axis coordinate as a floating-point number
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
</para>
</listitem>
</varlistentry>
</variablelist>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
</sect2>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<sect2>
<title>Line Segment</title>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>line</primary>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Line segments (<type>lseg</type>) are represented by pairs of points.
</para>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
<type>lseg</type> is specified using the following syntax:
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<synopsis>
( ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ( <replaceable>x2</replaceable> , <replaceable>y2</replaceable> ) )
( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ( <replaceable>x2</replaceable> , <replaceable>y2</replaceable> )
<replaceable>x1</replaceable> , <replaceable>y1</replaceable> , <replaceable>x2</replaceable> , <replaceable>y2</replaceable>
</synopsis>
where the arguments are
<variablelist>
<varlistentry>
<term>(<replaceable>x1</replaceable>,<replaceable>y1</replaceable>)</term>
<term>(<replaceable>x2</replaceable>,<replaceable>y2</replaceable>)</term>
<listitem>
<para>
proof-reading
2001-11-28 21:49:10 +01:00
The end points of the line segment
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
</para>
</listitem>
</varlistentry>
</variablelist>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
</sect2>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<sect2>
<title>Box</title>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>box (data type)</primary>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Replace incorrect uses of 'which' with 'that'. (so-called "wicked which")
2000-12-22 19:57:50 +01:00
Boxes are represented by pairs of points that are opposite
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
corners of the box.
</para>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<type>box</type> is specified using the following syntax:
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<synopsis>
( ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ( <replaceable>x2</replaceable> , <replaceable>y2</replaceable> ) )
( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ( <replaceable>x2</replaceable> , <replaceable>y2</replaceable> )
<replaceable>x1</replaceable> , <replaceable>y1</replaceable> , <replaceable>x2</replaceable> , <replaceable>y2</replaceable>
</synopsis>
where the arguments are
<variablelist>
<varlistentry>
<term>(<replaceable>x1</replaceable>,<replaceable>y1</replaceable>)</term>
<term>(<replaceable>x2</replaceable>,<replaceable>y2</replaceable>)</term>
<listitem>
<para>
proof-reading
2001-11-28 21:49:10 +01:00
Opposite corners of the box
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Boxes are output using the first syntax.
The corners are reordered on input to store
BOX documentation disagreed with code about corner order.
2001-03-10 22:16:32 +01:00
the upper right corner, then the lower left corner.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Other corners of the box can be entered, but the lower
left and upper right corners are determined from the input and stored.
</para>
</sect2>
<sect2>
<title>Path</title>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>path (data type)</primary>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Replace ASCII-quotes with proper markup.
2001-09-13 17:55:24 +02:00
Paths are represented by connected sets of points. Paths can be
<firstterm>open</firstterm>, where
the first and last points in the set are not connected, and <firstterm>closed</firstterm>,
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
where the first and last point are connected. Functions
<function>popen(p)</function>
and
<function>pclose(p)</function>
are supplied to force a path to be open or closed, and functions
<function>isopen(p)</function>
and
<function>isclosed(p)</function>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
are supplied to test for either type in a query.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
<para>
<type>path</type> is specified using the following syntax:
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<synopsis>
( ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ... , ( <replaceable>xn</replaceable> , <replaceable>yn</replaceable> ) )
[ ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ... , ( <replaceable>xn</replaceable> , <replaceable>yn</replaceable> ) ]
( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ... , ( <replaceable>xn</replaceable> , <replaceable>yn</replaceable> )
( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> , ... , <replaceable>xn</replaceable> , <replaceable>yn</replaceable> )
<replaceable>x1</replaceable> , <replaceable>y1</replaceable> , ... , <replaceable>xn</replaceable> , <replaceable>yn</replaceable>
</synopsis>
where the arguments are
<variablelist>
<varlistentry>
<term>(<replaceable>x</replaceable>,<replaceable>y</replaceable>)</term>
<listitem>
<para>
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
End points of the line segments comprising the path.
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
A leading square bracket ("[") indicates an open path, while
a leading parenthesis ("(") indicates a closed path.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Paths are output using the first syntax.
</para>
</sect2>
<sect2>
<title>Polygon</title>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>polygon</primary>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Polygons are represented by sets of points. Polygons should probably be
considered equivalent to closed paths, but are stored differently
and have their own set of support routines.
</para>
<para>
<type>polygon</type> is specified using the following syntax:
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<synopsis>
( ( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ... , ( <replaceable>xn</replaceable> , <replaceable>yn</replaceable> ) )
( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> ) , ... , ( <replaceable>xn</replaceable> , <replaceable>yn</replaceable> )
( <replaceable>x1</replaceable> , <replaceable>y1</replaceable> , ... , <replaceable>xn</replaceable> , <replaceable>yn</replaceable> )
<replaceable>x1</replaceable> , <replaceable>y1</replaceable> , ... , <replaceable>xn</replaceable> , <replaceable>yn</replaceable>
</synopsis>
where the arguments are
<variablelist>
<varlistentry>
<term>(<replaceable>x</replaceable>,<replaceable>y</replaceable>)</term>
<listitem>
<para>
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
End points of the line segments comprising the boundary of the
proof-reading
2001-11-28 21:49:10 +01:00
polygon
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Polygons are output using the first syntax.
</para>
</sect2>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<sect2>
<title>Circle</title>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>circle</primary>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Circles are represented by a center point and a radius.
</para>
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
<type>circle</type> is specified using the following syntax:
SGML source for new documentation.
1998-03-01 09:16:16 +01:00
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<synopsis>
&lt; ( <replaceable>x</replaceable> , <replaceable>y</replaceable> ) , <replaceable>r</replaceable> &gt;
( ( <replaceable>x</replaceable> , <replaceable>y</replaceable> ) , <replaceable>r</replaceable> )
( <replaceable>x</replaceable> , <replaceable>y</replaceable> ) , <replaceable>r</replaceable>
<replaceable>x</replaceable> , <replaceable>y</replaceable> , <replaceable>r</replaceable>
</synopsis>
where the arguments are
<variablelist>
<varlistentry>
<term>(<replaceable>x</replaceable>,<replaceable>y</replaceable>)</term>
<listitem>
<para>
proof-reading
2001-11-28 21:49:10 +01:00
Center of the circle
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><replaceable>r</replaceable></term>
<listitem>
<para>
proof-reading
2001-11-28 21:49:10 +01:00
Radius of the circle
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<para>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Circles are output using the first syntax.
</para>
</sect2>
</sect1>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect1 id="datatype-net-types">
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<title>Network Address Data Types</title>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm zone="datatype-net-types">
<primary>network</primary>
<secondary>addresses</secondary>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
<productname>PostgreSQL</> offers data types to store IP and MAC
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
addresses. It is preferable to use these types over plain text
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
types, because these types offer input error checking and several
specialized operators and functions.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<table tocentry="1" id="datatype-net-types-table">
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<title>Network Address Data Types</title>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<tgroup cols="4">
<thead>
<row>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<entry>Name</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<entry>Storage</entry>
<entry>Description</entry>
<entry>Range</entry>
</row>
</thead>
<tbody>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>cidr</type></entry>
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
<entry>12 bytes</entry>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<entry>IP networks</entry>
<entry>valid IPv4 networks</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</row>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>inet</type></entry>
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
<entry>12 bytes</entry>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<entry>IP hosts and networks</entry>
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
<entry>valid IPv4 hosts or networks</entry>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</row>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>macaddr</type></entry>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<entry>6 bytes</entry>
<entry>MAC addresses</entry>
<entry>customary formats</entry>
</row>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</tbody>
</tgroup>
</table>
</para>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<para>
IP v6 is not supported, yet.
</para>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect2 id="datatype-inet">
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
<title><type>inet</type></title>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>inet (data type)</primary>
</indexterm>
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
<para>
The <type>inet</type> type holds an IP host address, and
optionally the identity of the subnet it is in, all in one field.
The subnet identity is represented by the number of bits in the
Alter documentation of boolean type, add example. Someone figured that it wasn't clear that the "boolean type" was actually called "boolean". Add tip about "casting" booleans using CASE. Spell check whole file.
2001-02-14 20:37:26 +01:00
network part of the address (the <quote>netmask</quote>). If the netmask is 32,
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
then the value does not indicate a subnet, only a single host.
Note that if you want to accept networks only, you should use the
<type>cidr</type> type rather than <type>inet</type>.
</para>
<para>
The input format for this type is <replaceable
class="parameter">x.x.x.x/y</replaceable> where <replaceable
class="parameter">x.x.x.x</replaceable> is an IP address and
<replaceable class="parameter">y</replaceable> is the number of
bits in the netmask. If the <replaceable
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
class="parameter">/y</replaceable> part is left off, then the
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
netmask is 32, and the value represents just a single host.
On display, the <replaceable class="parameter">/y</replaceable>
portion is suppressed if the netmask is 32.
</para>
</sect2>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect2 id="datatype-cidr">
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<title><type>cidr</></title>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>cidr</primary>
</indexterm>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
The <type>cidr</type> type holds an IP network specification.
Input and output formats follow Classless Internet Domain Routing
conventions.
The format for
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
specifying classless networks is <replaceable
class="parameter">x.x.x.x/y</> where <replaceable
class="parameter">x.x.x.x</> is the network and <replaceable
class="parameter">y</> is the number of bits in the netmask. If
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<replaceable class="parameter">y</> is omitted, it is calculated
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
using assumptions from the older classful numbering system, except
that it will be at least large enough to include all of the octets
written in the input.
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
<para>
Here are some examples:
Include new cidr and inet data types.
1998-10-27 07:14:41 +01:00
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<table tocentry="1">
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<title><type>cidr</> Type Input Examples</title>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<tgroup cols="3">
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<thead>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>CIDR</type> Input</entry>
<entry><type>CIDR</type> Displayed</entry>
<entry><function>abbrev</function>(<type>CIDR</type>)</entry>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
</row>
</thead>
<tbody>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<row>
<entry>192.168.100.128/25</entry>
<entry>192.168.100.128/25</entry>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<entry>192.168.100.128/25</entry>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
</row>
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
<row>
<entry>192.168/24</entry>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<entry>192.168.0.0/24</entry>
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
<entry>192.168.0/24</entry>
</row>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<row>
<entry>192.168/25</entry>
<entry>192.168.0.0/25</entry>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<entry>192.168.0.0/25</entry>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
</row>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<row>
<entry>192.168.1</entry>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<entry>192.168.1.0/24</entry>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<entry>192.168.1/24</entry>
</row>
<row>
<entry>192.168</entry>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<entry>192.168.0.0/24</entry>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<entry>192.168.0/24</entry>
</row>
<row>
<entry>128.1</entry>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<entry>128.1.0.0/16</entry>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<entry>128.1/16</entry>
</row>
<row>
<entry>128</entry>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<entry>128.0.0.0/16</entry>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<entry>128.0/16</entry>
</row>
<row>
<entry>128.1.2</entry>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<entry>128.1.2.0/24</entry>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<entry>128.1.2/24</entry>
</row>
<row>
<entry>10.1.2</entry>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<entry>10.1.2.0/24</entry>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<entry>10.1.2/24</entry>
</row>
<row>
<entry>10.1</entry>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<entry>10.1.0.0/16</entry>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<entry>10.1/16</entry>
</row>
<row>
<entry>10</entry>
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<entry>10.0.0.0/8</entry>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<entry>10/8</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
Mention new AT TIME ZONE feature.
2000-11-11 20:50:31 +01:00
</sect2>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect2 id="datatype-inet-vs-cidr">
Repair markup
2000-11-12 00:27:48 +01:00
<title><type>inet</type> vs <type>cidr</type></title>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
<para>
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
The essential difference between <type>inet</type> and <type>cidr</type>
data types is that <type>inet</type> accepts values with nonzero bits to
the right of the netmask, whereas <type>cidr</type> does not.
<tip>
<para>
If you do not like the output format for <type>inet</type> or
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
<type>cidr</type> values, try the <function>host</>(),
<function>text</>(), and <function>abbrev</>() functions.
Adjust INET/CIDR display conventions and reimplement some INET/CIDR functions, per recent discussions on pghackers. For now, I have called the verbose-display formatting function text(), but will reconsider if enough people object. initdb forced.
2000-11-10 21:13:27 +01:00
</para>
</tip>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</para>
</sect2>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect2 id="datatype-macaddr">
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<title><type>macaddr</></>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>macaddr (data type)</primary>
</indexterm>
<indexterm>
<primary>MAC address</primary>
<see>macaddr</see>
</indexterm>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<para>
The <type>macaddr</> type stores MAC addresses, i.e., Ethernet
card hardware addresses (although MAC addresses are used for
other purposes as well). Input is accepted in various customary
Bunch of copy fitting and style sheet tweakage to get decent looking print output (from pdfjadetex). Also updated instructions to install documentation processing toolchain.
2001-10-09 20:46:00 +02:00
formats, including
<simplelist>
<member><literal>'08002b:010203'</></member>
<member><literal>'08002b-010203'</></member>
<member><literal>'0800.2b01.0203'</></member>
<member><literal>'08-00-2b-01-02-03'</></member>
<member><literal>'08:00:2b:01:02:03'</></member>
</simplelist>
which would all specify the same
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
address. Upper and lower case is accepted for the digits
<literal>a</> through <literal>f</>. Output is always in the
Bunch of copy fitting and style sheet tweakage to get decent looking print output (from pdfjadetex). Also updated instructions to install documentation processing toolchain.
2001-10-09 20:46:00 +02:00
last of the shown forms.
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
</para>
Add note about the availability of contrib/mac for the macaddr data type.
2001-02-10 19:02:35 +01:00
<para>
The directory <filename class="directory">contrib/mac</filename>
Bunch of copy fitting and style sheet tweakage to get decent looking print output (from pdfjadetex). Also updated instructions to install documentation processing toolchain.
2001-10-09 20:46:00 +02:00
in the <productname>PostgreSQL</productname> source distribution
Add note about the availability of contrib/mac for the macaddr data type.
2001-02-10 19:02:35 +01:00
contains tools that can be used to map MAC addresses to hardware
manufacturer names.
</para>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
</sect2>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</sect1>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<sect1 id="datatype-bit">
<title>Bit String Types</title>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm zone="datatype-bit">
<primary>bit strings</primary>
<secondary>data type</secondary>
</indexterm>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<para>
Bit strings are strings of 1's and 0's. They can be used to store
or visualize bit masks. There are two SQL bit types:
<type>BIT(<replaceable>x</replaceable>)</type> and <type>BIT
Make bit and bit varying types reject too long input. (They already tried to do that, but inconsistently.) Make bit type reject too short input, too, per SQL. Since it no longer zero pads, 'zpbit*' has been renamed to 'bit*' in the source, hence initdb.
2001-05-22 18:37:17 +02:00
VARYING(<replaceable>x</replaceable>)</type>; where
<replaceable>x</replaceable> is a positive integer.
</para>
<para>
<type>BIT</type> type data must match the length
<replaceable>x</replaceable> exactly; it is an error to attempt to
store shorter or longer bit strings. <type>BIT VARYING</type> is
of variable length up to the maximum length
<replaceable>x</replaceable>; longer strings will be rejected.
<type>BIT</type> without length is equivalent to
<literal>BIT(1)</literal>, <type>BIT VARYING</type> without length
specification means unlimited length.
</para>
<note>
<para>
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
Prior to <productname>PostgreSQL</> 7.2, <type>BIT</type> type data was
Make bit and bit varying types reject too long input. (They already tried to do that, but inconsistently.) Make bit type reject too short input, too, per SQL. Since it no longer zero pads, 'zpbit*' has been renamed to 'bit*' in the source, hence initdb.
2001-05-22 18:37:17 +02:00
zero-padded on the right. This was changed to comply with the
SQL standard. To implement zero-padded bit strings, a
combination of the concatenation operator and the
<function>substring</function> function can be used.
</para>
</note>
<para>
Refer to <xref
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
linkend="sql-syntax-bit-strings"> for information about the syntax
of bit string constants. Bit-logical operators and string
manipulation functions are available; see <xref
linkend="functions">.
</para>
Make bit and bit varying types reject too long input. (They already tried to do that, but inconsistently.) Make bit type reject too short input, too, per SQL. Since it no longer zero pads, 'zpbit*' has been renamed to 'bit*' in the source, hence initdb.
2001-05-22 18:37:17 +02:00
<example>
<title>Using the bit string types</title>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
<programlisting>
CREATE TABLE test (a BIT(3), b BIT VARYING(5));
INSERT INTO test VALUES (B'101', B'00');
Make bit and bit varying types reject too long input. (They already tried to do that, but inconsistently.) Make bit type reject too short input, too, per SQL. Since it no longer zero pads, 'zpbit*' has been renamed to 'bit*' in the source, hence initdb.
2001-05-22 18:37:17 +02:00
INSERT INTO test VALUES (B'10', B'101');
<computeroutput>
ERROR: bit string length does not match type bit(3)
</computeroutput>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
SELECT SUBSTRING(b FROM 1 FOR 2) FROM test;
</programlisting>
Make bit and bit varying types reject too long input. (They already tried to do that, but inconsistently.) Make bit type reject too short input, too, per SQL. Since it no longer zero pads, 'zpbit*' has been renamed to 'bit*' in the source, hence initdb.
2001-05-22 18:37:17 +02:00
</example>
Add information about bit types. Adjust some other things to promote SQL type names over internal type names.
2001-01-13 19:34:51 +01:00
</sect1>
Try to clarify characteristics of the SERIAL type. Fix source indenting, which does not affect output. Note: still need docs on NUMERIC and DECIMAL (and let's not talk about regression tests :()
1999-08-06 15:43:42 +02:00
</chapter>
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
<!-- Keep this comment at the end of the file
Local variables:
Minor markup changes. Refer to (".../catalog") in the emacs hints.
2000-03-31 05:27:42 +02:00
mode:sgml
Describe the date/time parsing rules. Include specific information on the supported time zones. It's a really big table, so maybe it should go into an appendix instead.
1999-02-13 04:42:10 +01:00
sgml-omittag:nil
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
sgml-indent-tabs-mode:nil
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:"./reference.ced"
sgml-exposed-tags:nil
Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-21 06:53:41 +01:00
sgml-local-catalogs:("/usr/share/sgml/catalog")
Update some info, especially the CIDR/INET data types.
1998-12-18 17:11:12 +01:00
sgml-local-ecat-files:nil
End:
-->