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/func.sgml

6646 lines
223 KiB
Plaintext
Raw Normal View History

Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
<!--
Grant options, and cascading revoke. Grant options are allowed only for users right now, not groups. Extension of has_foo_privileges functions to query the grant options. Extension of aclitem type to store grantor.
2003-01-24 00:39:07 +01:00
$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.136 2003/01/23 23:38:51 petere Exp $
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 documentation
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
-->
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<chapter id="functions">
<title>Functions and Operators</title>
<indexterm zone="functions">
<primary>functions</primary>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
</indexterm>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<indexterm zone="functions">
<primary>operators</primary>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
</indexterm>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<productname>PostgreSQL</productname> provides a large number of
functions and operators for the built-in data types. Users can also
define their own functions and operators, as described in the
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
&cite-programmer;. The
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<application>psql</application> commands <command>\df</command> and
<command>\do</command> can be used to show the list of all actually
available functions and operators, respectively.
</para>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
If you are concerned about portability then take note that most of
the functions and operators described in this chapter, with the
exception of the most trivial arithmetic and comparison operators
and some explicitly marked functions, are not specified by the
<acronym>SQL</acronym>
standard. Some of this extended functionality is present in other
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<acronym>SQL</acronym> implementations, and in many cases this
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
functionality is compatible and consistent between various products.
</para>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<sect1 id="functions-logical">
<title>Logical Operators</title>
<indexterm zone="functions-logical">
<primary>operators</primary>
<secondary>logical</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>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<primary>Boolean</primary>
<secondary>operators</secondary>
<see>operators, logical</see>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
</indexterm>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
The usual logical operators are available:
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<indexterm>
<primary>and</primary>
<secondary>operator</secondary>
</indexterm>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<indexterm>
<primary>or</primary>
<secondary>operator</secondary>
</indexterm>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<indexterm>
<primary>not</primary>
<secondary>operator</secondary>
</indexterm>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<simplelist>
<member>AND</member>
<member>OR</member>
<member>NOT</member>
</simplelist>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<acronym>SQL</acronym> uses a three-valued Boolean logic where the null value represents
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<quote>unknown</quote>. Observe the following truth tables:
<informaltable>
<tgroup cols="4">
<thead>
<row>
<entry><replaceable>a</replaceable></entry>
<entry><replaceable>b</replaceable></entry>
<entry><replaceable>a</replaceable> AND <replaceable>b</replaceable></entry>
<entry><replaceable>a</replaceable> OR <replaceable>b</replaceable></entry>
</row>
</thead>
<tbody>
<row>
<entry>TRUE</entry>
<entry>TRUE</entry>
<entry>TRUE</entry>
<entry>TRUE</entry>
</row>
<row>
<entry>TRUE</entry>
<entry>FALSE</entry>
<entry>FALSE</entry>
<entry>TRUE</entry>
</row>
<row>
<entry>TRUE</entry>
<entry>NULL</entry>
<entry>NULL</entry>
<entry>TRUE</entry>
</row>
<row>
<entry>FALSE</entry>
<entry>FALSE</entry>
<entry>FALSE</entry>
<entry>FALSE</entry>
</row>
<row>
<entry>FALSE</entry>
<entry>NULL</entry>
<entry>FALSE</entry>
<entry>NULL</entry>
</row>
<row>
<entry>NULL</entry>
<entry>NULL</entry>
<entry>NULL</entry>
<entry>NULL</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<informaltable>
<tgroup cols="2">
<thead>
<row>
<entry><replaceable>a</replaceable></entry>
<entry>NOT <replaceable>a</replaceable></entry>
</row>
</thead>
<tbody>
<row>
<entry>TRUE</entry>
<entry>FALSE</entry>
</row>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry>FALSE</entry>
<entry>TRUE</entry>
</row>
<row>
<entry>NULL</entry>
<entry>NULL</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
</sect1>
<sect1 id="functions-comparison">
<title>Comparison Operators</title>
<indexterm zone="functions-comparison">
<primary>comparison</primary>
<secondary>operators</secondary>
</indexterm>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
The usual comparison operators are available, shown in <xref
linkend="functions-comparison-table">.
</para>
<table id="functions-comparison-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title>Comparison Operators</title>
<tgroup cols="2">
<thead>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>Operator</entry>
<entry>Description</entry>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
</row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</thead>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<tbody>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>&lt;</literal> </entry>
<entry>less than</entry>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
</row>
AND/OR truth table needs another row IMHO.
2001-02-19 01:01:18 +01:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>&gt;</literal> </entry>
<entry>greater than</entry>
AND/OR truth table needs another row IMHO.
2001-02-19 01:01:18 +01:00
</row>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>&lt;=</literal> </entry>
<entry>less than or equal to</entry>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>&gt;=</literal> </entry>
<entry>greater than or equal to</entry>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>=</literal> </entry>
<entry>equal</entry>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>&lt;&gt;</literal> or <literal>!=</literal> </entry>
<entry>not equal</entry>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
</row>
</tbody>
</tgroup>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</table>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<note>
<para>
The <literal>!=</literal> operator is converted to
<literal>&lt;&gt;</literal> in the parser stage. It is not
possible to implement <literal>!=</literal> and
<literal>&lt;&gt;</literal> operators that do different things.
</para>
</note>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Minor updates for release.
1999-06-14 09:36:12 +02:00
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
Comparison operators are available for all data types where this
makes sense. All comparison operators are binary operators that
return values of type <type>boolean</type>; expressions like
<literal>1 &lt; 2 &lt; 3</literal> are not valid (because there is
no <literal>&lt;</literal> operator to compare a Boolean value with
<literal>3</literal>).
Minor updates for release.
1999-06-14 09:36:12 +02:00
</para>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
<indexterm>
<primary>between</primary>
</indexterm>
In addition to the comparison operators, the special
<token>BETWEEN</token> construct is available.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<synopsis>
Document BETWEEN.
2001-02-05 20:21:45 +01:00
<replaceable>a</replaceable> BETWEEN <replaceable>x</replaceable> AND <replaceable>y</replaceable>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</synopsis>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
is equivalent to
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<synopsis>
Fix markup, Alvaro Herrera.
2002-08-21 07:25:49 +02:00
<replaceable>a</replaceable> &gt;= <replaceable>x</replaceable> AND <replaceable>a</replaceable> &lt;= <replaceable>y</replaceable>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</synopsis>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
Similarly,
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<synopsis>
Document BETWEEN.
2001-02-05 20:21:45 +01:00
<replaceable>a</replaceable> NOT BETWEEN <replaceable>x</replaceable> AND <replaceable>y</replaceable>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</synopsis>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
is equivalent to
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<synopsis>
Fix markup, Alvaro Herrera.
2002-08-21 07:25:49 +02:00
<replaceable>a</replaceable> &lt; <replaceable>x</replaceable> OR <replaceable>a</replaceable> &gt; <replaceable>y</replaceable>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</synopsis>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
There is no difference between the two respective forms apart from
the <acronym>CPU</acronym> cycles required to rewrite the first one
into the second one internally.
</para>
Document BETWEEN.
2001-02-05 20:21:45 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
To check whether a value is or is not null, use the constructs
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<synopsis>
Description of table expressions, including join syntax, from Robert B. Easter <reaster@comptechnews.com>, heavily massaged by me. Also cleaned up value expressions a bit.
2001-01-21 23:02:01 +01:00
<replaceable>expression</replaceable> IS NULL
<replaceable>expression</replaceable> IS NOT NULL
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</synopsis>
or the equivalent, but nonstandard, constructs
<synopsis>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<replaceable>expression</replaceable> ISNULL
<replaceable>expression</replaceable> NOTNULL
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</synopsis>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</para>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
Do <emphasis>not</emphasis> write
<literal><replaceable>expression</replaceable> = NULL</literal>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
because <literal>NULL</> is not <quote>equal to</quote>
<literal>NULL</>. (The null value represents an unknown value,
and it is not known whether two unknown values are equal.)
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</para>
Add IS UNKNOWN, IS NOT UNKNOWN boolean tests, fix the existing boolean tests to return the correct results per SQL9x when given NULL inputs. Reimplement these tests as well as IS [NOT] NULL to have their own expression node types, instead of depending on special functions. From Joe Conway, with a little help from Tom Lane.
2001-06-20 00:39:12 +02:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
Some applications may (incorrectly) require that
<literal><replaceable>expression</replaceable> = NULL</literal>
returns true if <replaceable>expression</replaceable> evaluates to
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
the null value. To support these applications, the run-time option
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<varname>transform_null_equals</varname> can be turned on (e.g.,
<literal>SET transform_null_equals TO ON;</literal>).
<productname>PostgreSQL</productname> will then convert
<literal>x = NULL</literal> clauses to
<literal>x IS NULL</literal>. This was
the default behavior in releases 6.5 through 7.1.
</para>
Provide tunable knob for x = NULL -> x IS NULL transformation, default to off.
2001-09-20 16:20:28 +02:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
Boolean values can also be tested using the constructs
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<synopsis>
Add IS UNKNOWN, IS NOT UNKNOWN boolean tests, fix the existing boolean tests to return the correct results per SQL9x when given NULL inputs. Reimplement these tests as well as IS [NOT] NULL to have their own expression node types, instead of depending on special functions. From Joe Conway, with a little help from Tom Lane.
2001-06-20 00:39:12 +02:00
<replaceable>expression</replaceable> IS TRUE
<replaceable>expression</replaceable> IS NOT TRUE
<replaceable>expression</replaceable> IS FALSE
<replaceable>expression</replaceable> IS NOT FALSE
<replaceable>expression</replaceable> IS UNKNOWN
<replaceable>expression</replaceable> IS NOT UNKNOWN
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</synopsis>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
These are similar to <literal>IS NULL</literal> in that they will
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
always return true or false, never a null value, even when the operand is null.
A null input is treated as the logical value <quote>unknown</>.
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<sect1 id="functions-math">
<title>Mathematical Functions and Operators</title>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
Mathematical operators are provided for many
<productname>PostgreSQL</productname> types. For types without
common mathematical conventions for all possible permutations
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
(e.g., date/time types) we
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
describe the actual behavior in subsequent sections.
</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
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="functions-math-op-table"> shows the available mathematical operators.
</para>
<table id="functions-math-op-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title>Mathematical Operators</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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<tgroup cols="4">
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
<thead>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>Name</entry>
<entry>Description</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>Example</entry>
<entry>Result</entry>
</row>
</thead>
<tbody>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>+</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>addition</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>2 + 3</entry>
<entry>5</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>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +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
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>-</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>subtraction</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>2 - 3</entry>
<entry>-1</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>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +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
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>*</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>multiplication</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>2 * 3</entry>
<entry>6</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>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +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
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>/</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>division (integer division truncates results)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>4 / 2</entry>
<entry>2</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>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +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
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>%</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>modulo (remainder)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>5 % 4</entry>
<entry>1</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>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +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
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry> <literal>^</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>exponentiation</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>2.0 ^ 3.0</entry>
<entry>8</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>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> <literal>|/</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>square root</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>|/ 25.0</entry>
<entry>5</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> <literal>||/</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>cube root</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>||/ 27.0</entry>
<entry>3</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> <literal>!</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>factorial</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>5 !</entry>
<entry>120</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> <literal>!!</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>factorial (prefix operator)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>!! 5</entry>
<entry>120</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> <literal>@</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>absolute value</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>@ -5.0</entry>
<entry>5</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> <literal>&amp;</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>binary AND</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>91 & 15</entry>
<entry>11</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> <literal>|</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>binary OR</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>32 | 3</entry>
<entry>35</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> <literal>#</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>binary XOR</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>17 # 5</entry>
<entry>20</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> <literal>~</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>binary NOT</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>~1</entry>
<entry>-2</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> &lt;&lt; </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>binary shift left</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>1 &lt;&lt; 4</entry>
<entry>16</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> &gt;&gt; </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>binary shift right</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>8 &gt;&gt; 2</entry>
<entry>2</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</tbody>
</tgroup>
</table>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
The <quote>binary</quote> operators are also available for the bit
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
string types <type>BIT</type> and <type>BIT VARYING</type>, as
shown in <xref linkend="functions-math-bit-table">.
Bit string arguments to <literal>&</literal>, <literal>|</literal>,
and <literal>#</literal> must be of equal length. When bit
Document get/set bit/byte functions.
2002-12-05 05:38:30 +01:00
shifting, the original length of the string is preserved, as shown
in the table.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table id="functions-math-bit-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title>Bit String Binary Operators</title>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<tgroup cols="2">
<thead>
<row>
<entry>Example</entry>
<entry>Result</entry>
</row>
</thead>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<tbody>
<row>
<entry>B'10001' & B'01101'</entry>
<entry>00001</entry>
</row>
<row>
<entry>B'10001' | B'01101'</entry>
<entry>11101</entry>
</row>
<row>
<entry>B'10001' # B'01101'</entry>
<entry>11110</entry>
</row>
<row>
<entry>~ B'10001'</entry>
<entry>01110</entry>
</row>
<row>
Add more documentation about CURRENT_TIMESTAMP. Also, code < and > as &lt;/&gt; for cleaner SGML.
2002-10-05 21:03:16 +02:00
<entry>B'10001' &lt;&lt; 3</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>01000</entry>
</row>
<row>
Add more documentation about CURRENT_TIMESTAMP. Also, code < and > as &lt;/&gt; for cleaner SGML.
2002-10-05 21:03:16 +02:00
<entry>B'10001' &gt;&gt; 2</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>00100</entry>
</row>
</tbody>
</tgroup>
</table>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="functions-math-func-table"> shows the available
mathematical functions. In the table, <literal>dp</literal>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
indicates <type>double precision</type>. Many of these functions
are provided in multiple forms with different argument types.
Except where noted, any given form of a function returns the same
datatype as its argument.
The functions working with <type>double precision</type> data are mostly
implemented on top of the host system's C library; accuracy and behavior in
boundary cases may therefore vary depending on the host system.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table id="functions-math-func-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title>Mathematical Functions</title>
<tgroup cols="5">
<thead>
<row>
<entry>Function</entry>
<entry>Return Type</entry>
<entry>Description</entry>
<entry>Example</entry>
<entry>Result</entry>
</row>
</thead>
<tbody>
<row>
<entry><function>abs</function>(<replaceable>x</replaceable>)</entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>(same as <replaceable>x</>)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>absolute value</entry>
<entry><literal>abs(-17.4)</literal></entry>
<entry>17.4</entry>
</row>
<row>
<entry><function>cbrt</function>(<type>dp</type>)</entry>
<entry><type>dp</type></entry>
<entry>cube root</entry>
<entry><literal>cbrt(27.0)</literal></entry>
<entry>3</entry>
</row>
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>ceil</function>(<type>dp</type> or <type>numeric</type>)</entry>
<entry>(same as input)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>smallest integer not less than argument</entry>
<entry><literal>ceil(-42.8)</literal></entry>
<entry>-42</entry>
</row>
<row>
<entry><function>degrees</function>(<type>dp</type>)</entry>
<entry><type>dp</type></entry>
<entry>radians to degrees</entry>
<entry><literal>degrees(0.5)</literal></entry>
<entry>28.6478897565412</entry>
</row>
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>exp</function>(<type>dp</type> or <type>numeric</type>)</entry>
<entry>(same as input)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>exponential</entry>
<entry><literal>exp(1.0)</literal></entry>
<entry>2.71828182845905</entry>
</row>
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>floor</function>(<type>dp</type> or <type>numeric</type>)</entry>
<entry>(same as input)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>largest integer not greater than argument</entry>
<entry><literal>floor(-42.8)</literal></entry>
<entry>-43</entry>
</row>
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>ln</function>(<type>dp</type> or <type>numeric</type>)</entry>
<entry>(same as input)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>natural logarithm</entry>
<entry><literal>ln(2.0)</literal></entry>
<entry>0.693147180559945</entry>
</row>
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>log</function>(<type>dp</type> or <type>numeric</type>)</entry>
<entry>(same as input)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>base 10 logarithm</entry>
<entry><literal>log(100.0)</literal></entry>
<entry>2</entry>
</row>
<row>
<entry><function>log</function>(<parameter>b</parameter> <type>numeric</type>,
<parameter>x</parameter> <type>numeric</type>)</entry>
<entry><type>numeric</type></entry>
<entry>logarithm to base <parameter>b</parameter></entry>
<entry><literal>log(2.0, 64.0)</literal></entry>
<entry>6.0000000000</entry>
</row>
<row>
<entry><function>mod</function>(<parameter>y</parameter>,
<parameter>x</parameter>)</entry>
<entry>(same as argument types)</entry>
<entry>remainder of <parameter>y</parameter>/<parameter>x</parameter></entry>
<entry><literal>mod(9,4)</literal></entry>
<entry>1</entry>
</row>
<row>
<entry><function>pi</function>()</entry>
<entry><type>dp</type></entry>
<entry><quote>Pi</quote> constant</entry>
<entry><literal>pi()</literal></entry>
<entry>3.14159265358979</entry>
</row>
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>pow</function>(<parameter>x</parameter> <type>dp</type>,
<parameter>e</parameter> <type>dp</type>)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><type>dp</type></entry>
<entry>raise a number to exponent <parameter>e</parameter></entry>
<entry><literal>pow(9.0, 3.0)</literal></entry>
<entry>729</entry>
</row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<row>
<entry><function>pow</function>(<parameter>x</parameter> <type>numeric</type>,
<parameter>e</parameter> <type>numeric</type>)</entry>
<entry><type>numeric</type></entry>
<entry>raise a number to exponent <parameter>e</parameter></entry>
<entry><literal>pow(9.0, 3.0)</literal></entry>
<entry>729</entry>
</row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>radians</function>(<type>dp</type>)</entry>
<entry><type>dp</type></entry>
<entry>degrees to radians</entry>
<entry><literal>radians(45.0)</literal></entry>
<entry>0.785398163397448</entry>
</row>
<row>
<entry><function>random</function>()</entry>
<entry><type>dp</type></entry>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry>random value between 0.0 and 1.0</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>random()</literal></entry>
<entry></entry>
</row>
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>round</function>(<type>dp</type> or <type>numeric</type>)</entry>
<entry>(same as input)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>round to nearest integer</entry>
<entry><literal>round(42.4)</literal></entry>
<entry>42</entry>
</row>
<row>
<entry><function>round</function>(<parameter>v</parameter> <type>numeric</type>, <parameter>s</parameter> <type>integer</type>)</entry>
<entry><type>numeric</type></entry>
<entry>round to <parameter>s</parameter> decimal places</entry>
<entry><literal>round(42.4382, 2)</literal></entry>
<entry>42.44</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<!--
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>setseed</function>(<replaceable>new-seed</replaceable>)</entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>set seed for subsequent random() calls</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>setseed(0.54823)</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry></entry>
</row>
-->
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>sign</function>(<type>dp</type> or <type>numeric</type>)</entry>
<entry>(same as input)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>sign of the argument (-1, 0, +1)</entry>
<entry><literal>sign(-8.4)</literal></entry>
<entry>-1</entry>
</row>
Document the sign() function.
2001-09-20 18:41:26 +02:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>sqrt</function>(<type>dp</type> or <type>numeric</type>)</entry>
<entry>(same as input)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>square root</entry>
<entry><literal>sqrt(2.0)</literal></entry>
<entry>1.4142135623731</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>trunc</function>(<type>dp</type> or <type>numeric</type>)</entry>
<entry>(same as input)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>truncate toward zero</entry>
<entry><literal>trunc(42.8)</literal></entry>
<entry>42</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>trunc</function>(<parameter>v</parameter> <type>numeric</type>, <parameter>s</parameter> <type>integer</type>)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><type>numeric</type></entry>
<entry>truncate to <parameter>s</parameter> decimal places</entry>
<entry><literal>trunc(42.4382, 2)</literal></entry>
<entry>42.43</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</tbody>
</tgroup>
</table>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
Finally, <xref linkend="functions-math-trig-table"> shows the
available trigonometric functions. All trigonometric functions
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
take arguments and return values of type <type>double
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
precision</type>.
</para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table id="functions-math-trig-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title>Trigonometric Functions</title>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<tgroup cols="2">
<thead>
<row>
<entry>Function</entry>
<entry>Description</entry>
</row>
</thead>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<tbody>
<row>
<entry><function>acos</function>(<replaceable>x</replaceable>)</entry>
<entry>inverse cosine</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>asin</function>(<replaceable>x</replaceable>)</entry>
<entry>inverse sine</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>atan</function>(<replaceable>x</replaceable>)</entry>
<entry>inverse tangent</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>atan2</function>(<replaceable>x</replaceable>,
<replaceable>y</replaceable>)</entry>
<entry>inverse tangent of
Fix atan() description. Bruno Wolff III
2002-09-11 04:56:46 +02:00
<replaceable>x</replaceable>/<replaceable>y</replaceable></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>cos</function>(<replaceable>x</replaceable>)</entry>
<entry>cosine</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>cot</function>(<replaceable>x</replaceable>)</entry>
<entry>cotangent</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>sin</function>(<replaceable>x</replaceable>)</entry>
<entry>sine</entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>tan</function>(<replaceable>x</replaceable>)</entry>
<entry>tangent</entry>
</row>
</tbody>
</tgroup>
</table>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</sect1>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<sect1 id="functions-string">
<title>String Functions and Operators</title>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
This section describes functions and operators for examining and
manipulating string values. Strings in this context include values
of all the types <type>CHARACTER</type>, <type>CHARACTER
VARYING</type>, and <type>TEXT</type>. Unless otherwise noted, all
of the functions listed below work on all of these types, but be
wary of potential effects of the automatic padding when using the
<type>CHARACTER</type> type. Generally, the functions described
here also work on data of non-string types by converting that data
to a string representation first. Some functions also exist
natively for bit-string types.
</para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
<acronym>SQL</acronym> defines some string functions with a special syntax where
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
certain key words rather than commas are used to separate the
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
arguments. Details are in <xref linkend="functions-string-sql">.
These functions are also implemented using the regular syntax for
function invocation. (See <xref linkend="functions-string-other">.)
</para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<table id="functions-string-sql">
<title><acronym>SQL</acronym> String Functions and Operators</title>
<tgroup cols="5">
<thead>
<row>
<entry>Function</entry>
<entry>Return Type</entry>
<entry>Description</entry>
<entry>Example</entry>
<entry>Result</entry>
</row>
</thead>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<tbody>
<row>
<entry> <parameter>string</parameter> <literal>||</literal>
<parameter>string</parameter> </entry>
<entry> <type>text</type> </entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
String concatenation
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<indexterm>
<primary>character strings</primary>
<secondary>concatenation</secondary>
</indexterm>
</entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>'Post' || 'greSQL'</literal></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>PostgreSQL</literal></entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>bit_length</function>(<parameter>string</parameter>)</entry>
<entry><type>integer</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Number of bits in string</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>bit_length('jose')</literal></entry>
<entry><literal>32</literal></entry>
</row>
SQL function bit_length
2001-05-24 11:29:29 +02:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>char_length</function>(<parameter>string</parameter>) or <function>character_length</function>(<parameter>string</parameter>)</entry>
<entry><type>integer</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Number of characters in string
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<indexterm>
<primary>character strings</primary>
<secondary>length</secondary>
</indexterm>
<indexterm>
<primary>length</primary>
<secondary>character strings</secondary>
<see>character strings, length</see>
</indexterm>
</entry>
<entry><literal>char_length('jose')</literal></entry>
<entry><literal>4</literal></entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
<row>
<entry><function>convert</function>(<parameter>string</parameter>
using <parameter>conversion_name</parameter>)</entry>
<entry><type>text</type></entry>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry>
Change encoding using specified conversion name. Conversions
can be defined by <command>CREATE CONVERSION</command>. Also
there are some pre-defined conversion names. See <xref
linkend="conversion-names"> for available conversion
names.
</entry>
<entry><literal>convert('PostgreSQL' using iso_8859_1_to_utf_8)</literal></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>'PostgreSQL'</literal> in Unicode (UTF-8) encoding</entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>lower</function>(<parameter>string</parameter>)</entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Convert string to lower case</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>lower('TOM')</literal></entry>
<entry><literal>tom</literal></entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>octet_length</function>(<parameter>string</parameter>)</entry>
<entry><type>integer</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Number of bytes in string</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>octet_length('jose')</literal></entry>
<entry><literal>4</literal></entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>overlay</function>(<parameter>string</parameter> placing <parameter>string</parameter> from <type>integer</type> <optional>for <type>integer</type></optional>)</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Insert substring
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<indexterm>
<primary>overlay</primary>
</indexterm>
</entry>
<entry><literal>overlay('Txxxxas' placing 'hom' from 2 for 4)</literal></entry>
<entry><literal>Thomas</literal></entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>position</function>(<parameter>substring</parameter> in <parameter>string</parameter>)</entry>
<entry><type>integer</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Location of specified substring</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>position('om' in 'Thomas')</literal></entry>
<entry><literal>3</literal></entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>substring</function>(<parameter>string</parameter> <optional>from <type>integer</type></optional> <optional>for <type>integer</type></optional>)</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Extract substring
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<indexterm>
<primary>substring</primary>
</indexterm>
</entry>
<entry><literal>substring('Thomas' from 2 for 3)</literal></entry>
<entry><literal>hom</literal></entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><function>substring</function>(<parameter>string</parameter> from <replaceable>pattern</replaceable>)</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Extract substring matching POSIX regular expression
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<indexterm>
<primary>substring</primary>
</indexterm>
</entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>substring('Thomas' from '...$')</literal></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>mas</literal></entry>
</row>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<row>
<entry><function>substring</function>(<parameter>string</parameter> from <replaceable>pattern</replaceable> for <replaceable>escape</replaceable>)</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Extract substring matching SQL regular expression
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<indexterm>
<primary>substring</primary>
</indexterm>
</entry>
<entry><literal>substring('Thomas' from '%#"o_a#"_' for '#')</literal></entry>
<entry><literal>oma</literal></entry>
</row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry>
<function>trim</function>(<optional>leading | trailing | both</optional>
<optional><parameter>characters</parameter></optional> from
<parameter>string</parameter>)
</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Remove the longest string containing only the
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<parameter>characters</parameter> (a space by default) from the
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
beginning/end/both ends of the <parameter>string</parameter>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</entry>
<entry><literal>trim(both 'x' from 'xTomxx')</literal></entry>
<entry><literal>Tom</literal></entry>
</row>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>upper</function>(<parameter>string</parameter>)</entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Convert string to upper case</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>upper('tom')</literal></entry>
<entry><literal>TOM</literal></entry>
</row>
</tbody>
</tgroup>
</table>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<para>
Additional string manipulation functions are available and are
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
listed in <xref linkend="functions-string-other">. Some of them are used internally to implement the
<acronym>SQL</acronym>-standard string functions listed in <xref linkend="functions-string-sql">.
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
</para>
<table id="functions-string-other">
<title>Other String Functions</title>
<tgroup cols="5">
<thead>
<row>
<entry>Function</entry>
<entry>Return Type</entry>
<entry>Description</entry>
<entry>Example</entry>
<entry>Result</entry>
</row>
</thead>
<tbody>
<row>
<entry><function>ascii</function>(<type>text</type>)</entry>
<entry>integer</entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><acronym>ASCII</acronym> code of the first character of the argument.</entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>ascii('x')</literal></entry>
<entry><literal>120</literal></entry>
</row>
<row>
<entry><function>btrim</function>(<parameter>string</parameter> <type>text</type>, <parameter>trim</parameter> <type>text</type>)</entry>
<entry><type>text</type></entry>
<entry>
Remove (trim) the longest string consisting only of characters
in <parameter>trim</parameter> from the start and end of
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<parameter>string</parameter>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
</entry>
<entry><literal>btrim('xyxtrimyyx','xy')</literal></entry>
<entry><literal>trim</literal></entry>
</row>
<row>
<entry><function>chr</function>(<type>integer</type>)</entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Character with the given <acronym>ASCII</acronym> code</entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>chr(65)</literal></entry>
<entry><literal>A</literal></entry>
</row>
<row>
<entry>
<function>convert</function>(<parameter>string</parameter>
<type>text</type>,
<optional><parameter>src_encoding</parameter> <type>name</type>,</optional>
<parameter>dest_encoding</parameter> <type>name</type>)
</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Convert string to <parameter>dest_encoding</parameter>.
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
The original encoding is specified by
<parameter>src_encoding</parameter>. If
<parameter>src_encoding</parameter> is omitted, database
encoding is assumed.
</entry>
<entry><literal>convert('text_in_unicode', 'UNICODE', 'LATIN1')</literal></entry>
<entry><literal>text_in_unicode</literal> represented in ISO 8859-1</entry>
</row>
<row>
<entry>
<function>decode</function>(<parameter>string</parameter> <type>text</type>,
<parameter>type</parameter> <type>text</type>)
</entry>
<entry><type>bytea</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Decode binary data from <parameter>string</parameter> previously
encoded with <function>encode()</>. Parameter type is same as in <function>encode()</>.
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
</entry>
<entry><literal>decode('MTIzAAE=', 'base64')</literal></entry>
<entry><literal>123\000\001</literal></entry>
</row>
<row>
<entry>
<function>encode</function>(<parameter>data</parameter> <type>bytea</type>,
<parameter>type</parameter> <type>text</type>)
</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Encode binary data to <acronym>ASCII</acronym>-only representation. Supported
types are: base64, hex, escape.
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
</entry>
<entry><literal>encode('123\\000\\001', 'base64')</literal></entry>
<entry><literal>MTIzAAE=</literal></entry>
</row>
<row>
<entry><function>initcap</function>(<type>text</type>)</entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Convert first letter of each word (whitespace separated) to upper case</entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>initcap('hi thomas')</literal></entry>
<entry><literal>Hi Thomas</literal></entry>
</row>
<row>
<entry><function>length</function>(<parameter>string</parameter>)</entry>
<entry><type>integer</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Length of string
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<indexterm>
<primary>character strings</primary>
<secondary>length</secondary>
</indexterm>
<indexterm>
<primary>length</primary>
<secondary>character strings</secondary>
<see>character strings, length</see>
</indexterm>
</entry>
<entry><literal>length('jose')</literal></entry>
<entry><literal>4</literal></entry>
</row>
<row>
<entry>
<function>lpad</function>(<parameter>string</parameter> <type>text</type>,
<parameter>length</parameter> <type>integer</type>
<optional>, <parameter>fill</parameter> <type>text</type></optional>)
</entry>
<entry>text</entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Fill up the <parameter>string</parameter> to length
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<parameter>length</parameter> by prepending the characters
<parameter>fill</parameter> (a space by default). If the
<parameter>string</parameter> is already longer than
<parameter>length</parameter> then it is truncated (on the
right).
</entry>
<entry><literal>lpad('hi', 5, 'xy')</literal></entry>
<entry><literal>xyxhi</literal></entry>
</row>
<row>
<entry><function>ltrim</function>(<parameter>string</parameter> <type>text</type>, <parameter>text</parameter> <type>text</type>)</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Remove the longest string containing only characters from
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<parameter>trim</parameter> from the start of the string.
</entry>
<entry><literal>ltrim('zzzytrim','xyz')</literal></entry>
<entry><literal>trim</literal></entry>
</row>
Attached are two small patches to expose md5 as a user function -- including documentation and regression test mods. It seemed small and unobtrusive enough to not require a specific proposal on the hackers list -- but if not, let me know and I'll make a pitch. Otherwise, if there are no objections please apply. Joe Conway
2002-12-06 06:20:28 +01:00
<row>
<entry><function>md5</function>(<parameter>string</parameter> <type>text</type>)</entry>
<entry><type>text</type></entry>
<entry>
Calculates the MD5 hash of given string, returning the result in hex.
</entry>
<entry><literal>md5('abc')</literal></entry>
<entry><literal>900150983cd24fb0d6963f7d28e17f72</literal></entry>
</row>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<row>
<entry><function>pg_client_encoding</function>()</entry>
<entry><type>name</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Current client encoding name.
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
</entry>
<entry><literal>pg_client_encoding()</literal></entry>
<entry><literal>SQL_ASCII</literal></entry>
</row>
<row>
<entry><function>quote_ident</function>(<parameter>string</parameter> text)</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Return the given string suitably quoted to be used as an identifier
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
in an SQL query string.
Quotes are added only if necessary (i.e., if the string contains
non-identifier characters or would be case-folded).
Embedded quotes are properly doubled.
</entry>
<entry><literal>quote_ident('Foo')</literal></entry>
<entry><literal>"Foo"</literal></entry>
</row>
<row>
<entry><function>quote_literal</function>(<parameter>string</parameter> text)</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Return the given string suitably quoted to be used as a literal
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
in an SQL query string.
Embedded quotes and backslashes are properly doubled.
</entry>
<entry><literal>quote_literal('O\'Reilly')</literal></entry>
<entry><literal>'O''Reilly'</literal></entry>
</row>
<row>
<entry><function>repeat</function>(<type>text</type>, <type>integer</type>)</entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Repeat text a number of times</entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>repeat('Pg', 4)</literal></entry>
<entry><literal>PgPgPgPg</literal></entry>
</row>
<row>
<entry><function>replace</function>(<parameter>string</parameter> <type>text</type>,
<parameter>from</parameter> <type>text</type>,
<parameter>to</parameter> <type>text</type>)</entry>
<entry><type>text</type></entry>
<entry>Replace all occurrences in <parameter>string</parameter> of substring
<parameter>from</parameter> with substring <parameter>to</parameter>
</entry>
<entry><literal>replace('abcdefabcdef', 'cd', 'XX')</literal></entry>
<entry><literal>abXXefabXXef</literal></entry>
</row>
<row>
<entry>
<function>rpad</function>(<parameter>string</parameter> <type>text</type>,
<parameter>length</parameter> <type>integer</type>
<optional>, <parameter>fill</parameter> <type>text</type></optional>)
</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Fill up the <parameter>string</parameter> to length
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<parameter>length</parameter> by appending the characters
<parameter>fill</parameter> (a space by default). If the
<parameter>string</parameter> is already longer than
<parameter>length</parameter> then it is truncated.
</entry>
<entry><literal>rpad('hi', 5, 'xy')</literal></entry>
<entry><literal>hixyx</literal></entry>
</row>
<row>
<entry><function>rtrim</function>(<parameter>string</parameter>
text, <parameter>trim</parameter> text)</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Remove the longest string containing only characters from
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<parameter>trim</parameter> from the end of the string.
</entry>
<entry><literal>rtrim('trimxxxx','x')</literal></entry>
<entry><literal>trim</literal></entry>
</row>
<row>
<entry><function>split_part</function>(<parameter>string</parameter> <type>text</type>,
<parameter>delimiter</parameter> <type>text</type>,
<parameter>column</parameter> <type>integer</type>)</entry>
<entry><type>text</type></entry>
<entry>Split <parameter>string</parameter> on <parameter>delimiter</parameter>
returning the resulting (one based) <parameter>column</parameter> number.
</entry>
<entry><literal>split_part('abc~@~def~@~ghi','~@~',2)</literal></entry>
<entry><literal>def</literal></entry>
</row>
<row>
<entry><function>strpos</function>(<parameter>string</parameter>, <parameter>substring</parameter>)</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Locate specified substring (same as
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<literal>position(<parameter>substring</parameter> in
<parameter>string</parameter>)</literal>, but note the reversed
argument order)
</entry>
<entry><literal>strpos('high','ig')</literal></entry>
<entry><literal>2</literal></entry>
</row>
<row>
<entry><function>substr</function>(<parameter>string</parameter>, <parameter>from</parameter> <optional>, <parameter>count</parameter></optional>)</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Extract specified substring (same as
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<literal>substring(<parameter>string</parameter> from <parameter>from</parameter> for <parameter>count</parameter>)</literal>)
</entry>
<entry><literal>substr('alphabet', 3, 2)</literal></entry>
<entry><literal>ph</literal></entry>
</row>
<row>
<entry><function>to_ascii</function>(<type>text</type>
<optional>, <parameter>encoding</parameter></optional>)</entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>
Convert text to <acronym>ASCII</acronym> from other encoding
<footnote>
<para>
The <function>to_ascii</function> function supports conversion from
<literal>LATIN1</>, <literal>LATIN2</>, and <literal>WIN1250</> only.
</para>
</footnote>
</entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>to_ascii('Karel')</literal></entry>
<entry><literal>Karel</literal></entry>
</row>
<row>
<entry><function>to_hex</function>(<parameter>number</parameter> <type>integer</type>
or <type>bigint</type>)</entry>
<entry><type>text</type></entry>
<entry>Convert <parameter>number</parameter> to its equivalent hexadecimal
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
representation
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
</entry>
<entry><literal>to_hex(9223372036854775807::bigint)</literal></entry>
<entry><literal>7fffffffffffffff</literal></entry>
</row>
<row>
<entry>
<function>translate</function>(<parameter>string</parameter>
<type>text</type>,
<parameter>from</parameter> <type>text</type>,
<parameter>to</parameter> <type>text</type>)
</entry>
<entry><type>text</type></entry>
<entry>
Any character in <parameter>string</parameter> that matches a
character in the <parameter>from</parameter> set is replaced by
the corresponding character in the <parameter>to</parameter>
set.
</entry>
<entry><literal>translate('12345', '14', 'ax')</literal></entry>
<entry><literal>a23x5</literal></entry>
</row>
</tbody>
</tgroup>
</table>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
<table id="conversion-names">
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<title>Built-in Conversions</title>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
<tgroup cols="3">
<thead>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry>Conversion Name
<footnote>
<para>
The conversion names follow a standard naming scheme: The
official name of the source encoding with all
non-alphanumeric characters replaced by underscores followed
by <literal>_to_</literal> followed by the equally processed
destination encoding name. Therefore the names might deviate
from the customary encoding names.
</para>
</footnote>
</entry>
<entry>Source Encoding</entry>
<entry>Destination Encoding</entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
</thead>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
<tbody>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>ascii_to_mic</literal></entry>
<entry><literal>SQL_ASCII</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>ascii_to_utf_8</literal></entry>
<entry><literal>SQL_ASCII</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>big5_to_euc_tw</literal></entry>
<entry><literal>BIG5</literal></entry>
<entry><literal>EUC_TW</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>big5_to_mic</literal></entry>
<entry><literal>BIG5</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>big5_to_utf_8</literal></entry>
<entry><literal>BIG5</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>euc_cn_to_mic</literal></entry>
<entry><literal>EUC_CN</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>euc_cn_to_utf_8</literal></entry>
<entry><literal>EUC_CN</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>euc_jp_to_mic</literal></entry>
<entry><literal>EUC_JP</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>euc_jp_to_sjis</literal></entry>
<entry><literal>EUC_JP</literal></entry>
<entry><literal>SJIS</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>euc_jp_to_utf_8</literal></entry>
<entry><literal>EUC_JP</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>euc_kr_to_mic</literal></entry>
<entry><literal>EUC_KR</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>euc_kr_to_utf_8</literal></entry>
<entry><literal>EUC_KR</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>euc_tw_to_big5</literal></entry>
<entry><literal>EUC_TW</literal></entry>
<entry><literal>BIG5</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>euc_tw_to_mic</literal></entry>
<entry><literal>EUC_TW</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>euc_tw_to_utf_8</literal></entry>
<entry><literal>EUC_TW</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>gb18030_to_utf_8</literal></entry>
<entry><literal>GB18030</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>gbk_to_utf_8</literal></entry>
<entry><literal>GBK</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_10_to_utf_8</literal></entry>
<entry><literal>LATIN6</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_13_to_utf_8</literal></entry>
<entry><literal>LATIN7</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_14_to_utf_8</literal></entry>
<entry><literal>LATIN8</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_15_to_utf_8</literal></entry>
<entry><literal>LATIN9</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_16_to_utf_8</literal></entry>
<entry><literal>LATIN10</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_1_to_mic</literal></entry>
<entry><literal>LATIN1</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_1_to_utf_8</literal></entry>
<entry><literal>LATIN1</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_2_to_mic</literal></entry>
<entry><literal>LATIN2</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_2_to_utf_8</literal></entry>
<entry><literal>LATIN2</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>iso_8859_2_to_windows_1250</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>LATIN2</literal></entry>
<entry><literal>WIN1250</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_3_to_mic</literal></entry>
<entry><literal>LATIN3</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_3_to_utf_8</literal></entry>
<entry><literal>LATIN3</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_4_to_mic</literal></entry>
<entry><literal>LATIN4</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_4_to_utf_8</literal></entry>
<entry><literal>LATIN4</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>iso_8859_5_to_koi8_r</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>ISO_8859_5</literal></entry>
<entry><literal>KOI8</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_5_to_mic</literal></entry>
<entry><literal>ISO_8859_5</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_5_to_utf_8</literal></entry>
<entry><literal>ISO_8859_5</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>iso_8859_5_to_windows_1251</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>ISO_8859_5</literal></entry>
<entry><literal>WIN</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>iso_8859_5_to_windows_866</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>ISO_8859_5</literal></entry>
<entry><literal>ALT</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_6_to_utf_8</literal></entry>
<entry><literal>ISO_8859_6</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_7_to_utf_8</literal></entry>
<entry><literal>ISO_8859_7</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_8_to_utf_8</literal></entry>
<entry><literal>ISO_8859_8</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>iso_8859_9_to_utf_8</literal></entry>
<entry><literal>LATIN5</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>johab_to_utf_8</literal></entry>
<entry><literal>JOHAB</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>koi8_r_to_iso_8859_5</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>KOI8</literal></entry>
<entry><literal>ISO_8859_5</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>koi8_r_to_mic</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>KOI8</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>koi8_r_to_utf_8</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>KOI8</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>koi8_r_to_windows_1251</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>KOI8</literal></entry>
<entry><literal>WIN</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>koi8_r_to_windows_866</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>KOI8</literal></entry>
<entry><literal>ALT</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_ascii</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>SQL_ASCII</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_big5</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>BIG5</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_euc_cn</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>EUC_CN</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_euc_jp</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>EUC_JP</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_euc_kr</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>EUC_KR</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_euc_tw</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>EUC_TW</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_iso_8859_1</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>LATIN1</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_iso_8859_2</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>LATIN2</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_iso_8859_3</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>LATIN3</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_iso_8859_4</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>LATIN4</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_iso_8859_5</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>ISO_8859_5</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>mic_to_koi8_r</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>KOI8</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>mic_to_sjis</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>SJIS</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>mic_to_windows_1250</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>WIN1250</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>mic_to_windows_1251</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>WIN</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>mic_to_windows_866</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>ALT</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>sjis_to_euc_jp</literal></entry>
<entry><literal>SJIS</literal></entry>
<entry><literal>EUC_JP</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>sjis_to_mic</literal></entry>
<entry><literal>SJIS</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>sjis_to_utf_8</literal></entry>
<entry><literal>SJIS</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>tcvn_to_utf_8</literal></entry>
<entry><literal>TCVN</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>uhc_to_utf_8</literal></entry>
<entry><literal>UHC</literal></entry>
<entry><literal>UNICODE</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_ascii</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>SQL_ASCII</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_big5</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>BIG5</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_euc_cn</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>EUC_CN</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_euc_jp</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>EUC_JP</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_euc_kr</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>EUC_KR</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_euc_tw</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>EUC_TW</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_gb18030</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>GB18030</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_gbk</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>GBK</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_1</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>LATIN1</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_10</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>LATIN6</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_13</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>LATIN7</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_14</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>LATIN8</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_15</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>LATIN9</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_16</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>LATIN10</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_2</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>LATIN2</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_3</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>LATIN3</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_4</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>LATIN4</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_5</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>ISO_8859_5</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_6</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>ISO_8859_6</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_7</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>ISO_8859_7</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_8</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>ISO_8859_8</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_iso_8859_9</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>LATIN5</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_johab</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>JOHAB</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>utf_8_to_koi8_r</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>UNICODE</literal></entry>
<entry><literal>KOI8</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_sjis</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>SJIS</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_tcvn</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>TCVN</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
<row>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>utf_8_to_uhc</literal></entry>
<entry><literal>UNICODE</literal></entry>
<entry><literal>UHC</literal></entry>
Add SQL99 CONVERT() function.
2002-08-06 07:40:47 +02:00
</row>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>utf_8_to_windows_1250</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>UNICODE</literal></entry>
<entry><literal>WIN1250</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>utf_8_to_windows_1251</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>UNICODE</literal></entry>
<entry><literal>WIN</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>utf_8_to_windows_1256</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>UNICODE</literal></entry>
<entry><literal>WIN1256</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>utf_8_to_windows_866</literal></entry>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<entry><literal>UNICODE</literal></entry>
<entry><literal>ALT</literal></entry>
Add Cyrillic and other encodings for encoding conversion. Patches submitted by Kaori Inaba (i-kaori@sra.co.jp).
2002-08-14 04:45:10 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>utf_8_to_windows_874</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>UNICODE</literal></entry>
<entry><literal>WIN874</literal></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_1250_to_iso_8859_2</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>WIN1250</literal></entry>
<entry><literal>LATIN2</literal></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Document quote_ident and quote_literal in the main list of string functions, as suggested by Josh Berkus.
2002-06-25 00:17:01 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_1250_to_mic</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>WIN1250</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Document quote_ident and quote_literal in the main list of string functions, as suggested by Josh Berkus.
2002-06-25 00:17:01 +02:00
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_1250_to_utf_8</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>WIN1250</literal></entry>
<entry><literal>UNICODE</literal></entry>
Document quote_ident and quote_literal in the main list of string functions, as suggested by Josh Berkus.
2002-06-25 00:17:01 +02:00
</row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_1251_to_iso_8859_5</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>WIN</literal></entry>
<entry><literal>ISO_8859_5</literal></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Here's a doc patch for the new string functions recently committed -- replace, split, and to_hex. The patch also moves encode and decode into alphabetical order (since everything else in the table was). Joe Conway
2002-09-02 07:53:23 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_1251_to_koi8_r</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>WIN</literal></entry>
<entry><literal>KOI8</literal></entry>
Here's a doc patch for the new string functions recently committed -- replace, split, and to_hex. The patch also moves encode and decode into alphabetical order (since everything else in the table was). Joe Conway
2002-09-02 07:53:23 +02:00
</row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_1251_to_mic</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>WIN</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_1251_to_utf_8</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>WIN</literal></entry>
<entry><literal>UNICODE</literal></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Here's a doc patch for the new string functions recently committed -- replace, split, and to_hex. The patch also moves encode and decode into alphabetical order (since everything else in the table was). Joe Conway
2002-09-02 07:53:23 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_1251_to_windows_866</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>WIN</literal></entry>
<entry><literal>ALT</literal></entry>
Here's a doc patch for the new string functions recently committed -- replace, split, and to_hex. The patch also moves encode and decode into alphabetical order (since everything else in the table was). Joe Conway
2002-09-02 07:53:23 +02:00
</row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_1256_to_utf_8</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>WIN1256</literal></entry>
<entry><literal>UNICODE</literal></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_866_to_iso_8859_5</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>ALT</literal></entry>
<entry><literal>ISO_8859_5</literal></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</row>
> > Put encode() into base system. Used part of Alex' patch > > for docs, hope he does not mind ;) Marko Kreen
2001-07-12 00:14:03 +02:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_866_to_koi8_r</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>ALT</literal></entry>
<entry><literal>KOI8</literal></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Here's a doc patch for the new string functions recently committed -- replace, split, and to_hex. The patch also moves encode and decode into alphabetical order (since everything else in the table was). Joe Conway
2002-09-02 07:53:23 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_866_to_mic</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>ALT</literal></entry>
<entry><literal>MULE_INTERNAL</literal></entry>
Here's a doc patch for the new string functions recently committed -- replace, split, and to_hex. The patch also moves encode and decode into alphabetical order (since everything else in the table was). Joe Conway
2002-09-02 07:53:23 +02:00
</row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_866_to_utf_8</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>ALT</literal></entry>
<entry><literal>UNICODE</literal></entry>
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_866_to_windows_1251</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>ALT</literal></entry>
<entry><literal>WIN</literal></entry>
</row>
<row>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<entry><literal>windows_874_to_utf_8</literal></entry>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<entry><literal>WIN874</literal></entry>
<entry><literal>UNICODE</literal></entry>
</row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</tbody>
</tgroup>
</table>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</sect1>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<sect1 id="functions-binarystring">
<title>Binary String Functions and Operators</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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
This section describes functions and operators for examining and
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
manipulating binary string values. Strings in this context mean
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
values of the type <type>BYTEA</type>.
</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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
<acronym>SQL</acronym> defines some string functions with a
special syntax where
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
certain key words rather than commas are used to separate the
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
arguments. Details are in
<xref linkend="functions-binarystring-sql">.
Some functions are also implemented using the regular syntax for
function invocation.
(See <xref linkend="functions-binarystring-other">.)
</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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<table id="functions-binarystring-sql">
<title><acronym>SQL</acronym> Binary String Functions and Operators</title>
<tgroup cols="5">
<thead>
<row>
<entry>Function</entry>
<entry>Return Type</entry>
<entry>Description</entry>
<entry>Example</entry>
<entry>Result</entry>
</row>
</thead>
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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<tbody>
<row>
<entry> <parameter>string</parameter> <literal>||</literal>
<parameter>string</parameter> </entry>
<entry> <type>bytea</type> </entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
String concatenation
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<indexterm>
<primary>binary strings</primary>
<secondary>concatenation</secondary>
</indexterm>
</entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>'\\\\Post'::bytea || '\\047greSQL\\000'::bytea</literal></entry>
<entry><literal>\\Post'greSQL\000</literal></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</row>
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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>octet_length</function>(<parameter>string</parameter>)</entry>
<entry><type>integer</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Number of bytes in binary string</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>octet_length('jo\\000se'::bytea)</literal></entry>
<entry><literal>5</literal></entry>
</row>
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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>position</function>(<parameter>substring</parameter> in <parameter>string</parameter>)</entry>
<entry><type>integer</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Location of specified substring</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>position('\\000om'::bytea in 'Th\\000omas'::bytea)</literal></entry>
<entry><literal>3</literal></entry>
</row>
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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry><function>substring</function>(<parameter>string</parameter> <optional>from <type>integer</type></optional> <optional>for <type>integer</type></optional>)</entry>
<entry><type>bytea</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Extract substring
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<indexterm>
<primary>substring</primary>
</indexterm>
</entry>
<entry><literal>substring('Th\\000omas'::bytea from 2 for 3)</literal></entry>
<entry><literal>h\000o</literal></entry>
</row>
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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry>
<function>trim</function>(<optional>both</optional>
<parameter>characters</parameter> from
<parameter>string</parameter>)
</entry>
<entry><type>bytea</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Remove the longest string containing only the
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<parameter>characters</parameter> from the
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
beginning/end/both ends of the <parameter>string</parameter>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</entry>
<entry><literal>trim('\\000'::bytea from '\\000Tom\\000'::bytea)</literal></entry>
<entry><literal>Tom</literal></entry>
</row>
Document get/set bit/byte functions.
2002-12-05 05:38:30 +01:00
<row>
<entry><function>get_byte</function>(<parameter>string</parameter>, <parameter>offset</parameter>)</entry>
<entry><type>integer</type></entry>
<entry>
Extract byte from string.
<indexterm>
<primary>get_byte</primary>
</indexterm>
</entry>
<entry><literal>get_byte('Th\\000omas'::bytea, 4)</literal></entry>
<entry><literal>109</literal></entry>
</row>
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>set_byte</function>(<parameter>string</parameter>,
<parameter>offset</parameter>, <parameter>newvalue</>)</entry>
Document get/set bit/byte functions.
2002-12-05 05:38:30 +01:00
<entry><type>bytea</type></entry>
<entry>
Set byte in string.
<indexterm>
<primary>set_byte</primary>
</indexterm>
</entry>
<entry><literal>set_byte('Th\\000omas'::bytea, 4, 64)</literal></entry>
<entry><literal>Th\000o@as</literal></entry>
</row>
<row>
<entry><function>get_bit</function>(<parameter>string</parameter>, <parameter>offset</parameter>)</entry>
<entry><type>integer</type></entry>
<entry>
Extract bit from string.
<indexterm>
<primary>get_bit</primary>
</indexterm>
</entry>
<entry><literal>get_bit('Th\\000omas'::bytea, 45)</literal></entry>
<entry><literal>1</literal></entry>
</row>
<row>
Update 'Mathematical Functions' table to reflect 7.3 addition of float8 forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
2003-01-23 02:22:59 +01:00
<entry><function>set_bit</function>(<parameter>string</parameter>,
<parameter>offset</parameter>, <parameter>newvalue</>)</entry>
Document get/set bit/byte functions.
2002-12-05 05:38:30 +01:00
<entry><type>bytea</type></entry>
<entry>
Set bit in string.
<indexterm>
<primary>set_bit</primary>
</indexterm>
</entry>
<entry><literal>set_bit('Th\\000omas'::bytea, 45, 0)</literal></entry>
<entry><literal>Th\000omAs</literal></entry>
</row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</tbody>
</tgroup>
</table>
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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Additional binary string manipulation functions are available and
are listed in <xref linkend="functions-binarystring-other">. Some
of them are used internally to implement the
<acronym>SQL</acronym>-standard string functions listed in <xref
linkend="functions-binarystring-sql">.
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<table id="functions-binarystring-other">
<title>Other Binary String Functions</title>
<tgroup cols="5">
<thead>
<row>
<entry>Function</entry>
<entry>Return Type</entry>
<entry>Description</entry>
<entry>Example</entry>
<entry>Result</entry>
</row>
</thead>
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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<tbody>
<row>
<entry><function>btrim</function>(<parameter>string</parameter>
<type>bytea</type> <parameter>trim</parameter> <type>bytea</type>)</entry>
<entry><type>bytea</type></entry>
<entry>
Remove (trim) the longest string consisting only of characters
in <parameter>trim</parameter> from the start and end of
<parameter>string</parameter>.
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>
<entry><literal>btrim('\\000trim\\000'::bytea,'\\000'::bytea)</literal></entry>
<entry><literal>trim</literal></entry>
</row>
<row>
<entry><function>length</function>(<parameter>string</parameter>)</entry>
<entry><type>integer</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Length of binary 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
<indexterm>
<primary>binary strings</primary>
<secondary>length</secondary>
</indexterm>
<indexterm>
<primary>length</primary>
<secondary>binary strings</secondary>
<see>binary strings, length</see>
</indexterm>
</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>length('jo\\000se'::bytea)</literal></entry>
<entry><literal>5</literal></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>
<function>encode</function>(<parameter>string</parameter> <type>bytea</type>,
<parameter>type</parameter> <type>text</type>)
</entry>
<entry><type>text</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Encode binary string to <acronym>ASCII</acronym>-only representation. Supported
types are: base64, hex, escape.
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>
<entry><literal>encode('123\\000456'::bytea, 'escape')</literal></entry>
<entry><literal>123\000456</literal></entry>
</row>
<row>
<entry>
<function>decode</function>(<parameter>string</parameter> <type>text</type>,
<parameter>type</parameter> <type>text</type>)
</entry>
<entry><type>bytea</type></entry>
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Decode binary string from <parameter>string</parameter> previously
encoded with <literal>encode()</>. Parameter type is same as in <literal>encode()</>.
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>
<entry><literal>decode('123\\000456', 'escape')</literal></entry>
<entry><literal>123\000456</literal></entry>
</row>
</tbody>
</tgroup>
</table>
</sect1>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<sect1 id="functions-matching">
<title>Pattern Matching</title>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
There are three separate approaches to pattern matching provided by
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<productname>PostgreSQL</productname>: the traditional
<acronym>SQL</acronym>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<function>LIKE</function> operator, the more recent
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<acronym>SQL99</acronym>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<function>SIMILAR TO</function> operator, and
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<acronym>POSIX</acronym>-style regular expressions.
Additionally, a pattern matching function,
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<function>SUBSTRING</function>, is available, using either
<acronym>SQL99</acronym>-style or POSIX-style regular expressions.
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</para>
<tip>
<para>
If you have pattern matching needs that go beyond this,
consider writing a user-defined function in Perl or Tcl.
</para>
</tip>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<sect2 id="functions-like">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title><function>LIKE</function></title>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +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>like</primary>
</indexterm>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<synopsis>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<replaceable>string</replaceable> LIKE <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
<replaceable>string</replaceable> NOT LIKE <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</synopsis>
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
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<para>
Every <replaceable>pattern</replaceable> defines a set of strings.
The <function>LIKE</function> expression returns true if the
<replaceable>string</replaceable> is contained in the set of
strings represented by <replaceable>pattern</replaceable>. (As
expected, the <function>NOT LIKE</function> expression returns
false if <function>LIKE</function> returns true, and vice versa.
An equivalent expression is
<literal>NOT (<replaceable>string</replaceable> LIKE
<replaceable>pattern</replaceable>)</literal>.)
</para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
If <replaceable>pattern</replaceable> does not contain percent
signs or underscore, then the pattern only represents the string
itself; in that case <function>LIKE</function> acts like the
equals operator. An underscore (<literal>_</literal>) in
<replaceable>pattern</replaceable> stands for (matches) any single
character; a percent sign (<literal>%</literal>) matches any string
of zero or more characters.
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
Some examples:
<programlisting>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
'abc' LIKE 'abc' <lineannotation>true</lineannotation>
'abc' LIKE 'a%' <lineannotation>true</lineannotation>
'abc' LIKE '_b_' <lineannotation>true</lineannotation>
'abc' LIKE 'c' <lineannotation>false</lineannotation>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</programlisting>
</para>
Minor updates for release.
1999-06-14 09:36:12 +02:00
<para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<function>LIKE</function> pattern matches always cover the entire
A little wordsmithing in the pattern-matching section.
2000-12-16 20:33:23 +01:00
string. To match a pattern anywhere within a string, the
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
pattern must therefore start and end with a percent sign.
Minor updates for release.
1999-06-14 09:36:12 +02:00
</para>
Add exp(), ln(), and some other functions to numeric-functions table.
2000-03-20 05:20:52 +01:00
<para>
A little wordsmithing in the pattern-matching section.
2000-12-16 20:33:23 +01:00
To match a literal underscore or percent sign without matching
other characters, the respective character in
<replaceable>pattern</replaceable> must be
preceded by the escape character. The default escape
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
character is the backslash but a different one may be selected by
A little wordsmithing in the pattern-matching section.
2000-12-16 20:33:23 +01:00
using the <literal>ESCAPE</literal> clause. To match the escape
character itself, write two escape characters.
</para>
<para>
Note that the backslash already has a special meaning in string
literals, so to write a pattern constant that contains a backslash
Mention that LIKE ... ESCAPE '' is allowed to specify no escape character.
2001-11-18 22:17:10 +01:00
you must write two backslashes in the query. Thus, writing a pattern
that actually matches a literal backslash means writing four backslashes
in the query. You can avoid this by selecting a different escape
proof-reading
2001-11-28 21:49:10 +01:00
character with <literal>ESCAPE</literal>; then backslash is not special
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
to <function>LIKE</function> anymore. (But it is still special to the string
Mention that LIKE ... ESCAPE '' is allowed to specify no escape character.
2001-11-18 22:17:10 +01:00
literal parser, so you still need two of them.)
</para>
<para>
It's also possible to select no escape character by writing
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<literal>ESCAPE ''</literal>. This effectively disables the
Fix for documention: >>" It's also possible to select no escape character by writing ESCAPE ''. >>In this case there is no way to turn off the special meaning of >>underscore and percent signs in the pattern." Joe Conway
2002-08-22 06:56:44 +02:00
escape mechanism, which makes it impossible to turn off the
special meaning of underscore and percent signs in the pattern.
Add exp(), ln(), and some other functions to numeric-functions table.
2000-03-20 05:20:52 +01:00
</para>
Fix path to initdb in installation instructions. General cleanup for 7.0.
2000-04-07 15:30:58 +02:00
<para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
The keyword <token>ILIKE</token> can be used instead of
<token>LIKE</token> to make the match case insensitive according
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
to the active locale. This is not in the <acronym>SQL</acronym> standard but is a
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> extension.
Update some porting info. Add mention of transcendental functions.
2000-04-08 04:16:08 +02:00
</para>
Fix path to initdb in installation instructions. General cleanup for 7.0.
2000-04-07 15:30:58 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<para>
The operator <literal>~~</literal> is equivalent to
A little wordsmithing in the pattern-matching section.
2000-12-16 20:33:23 +01:00
<function>LIKE</function>, and <literal>~~*</literal> corresponds to
<function>ILIKE</function>. There are also
<literal>!~~</literal> and <literal>!~~*</literal> operators that
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
represent <function>NOT LIKE</function> and <function>NOT
Mention that LIKE ... ESCAPE '' is allowed to specify no escape character.
2001-11-18 22:17:10 +01:00
ILIKE</function>. All of these operators are
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>-specific.
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</para>
</sect2>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<sect2 id="functions-sql99-regexp">
<title><function>SIMILAR TO</function> and <acronym>SQL99</acronym>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
Regular Expressions</title>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<indexterm zone="functions-sql99-regexp">
<primary>regular expressions</primary>
Tweak conversion names to follow the established naming scheme, and document that scheme.
2002-09-24 22:14:59 +02:00
<!-- <seealso>pattern matching</seealso> breaks index build -->
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
</indexterm>
<indexterm>
<primary>similar to</primary>
</indexterm>
<indexterm>
<primary>substring</primary>
</indexterm>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<synopsis>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<replaceable>string</replaceable> SIMILAR TO <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
<replaceable>string</replaceable> NOT SIMILAR TO <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</synopsis>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<para>
The <function>SIMILAR TO</function> operator returns true or false
depending on whether its pattern matches the given string. It is
much like <function>LIKE</function>, except that it interprets the
pattern using <acronym>SQL99</acronym>'s definition of a regular
expression.
<acronym>SQL99</acronym>'s regular expressions are a curious cross
between <function>LIKE</function> notation and common regular expression
notation.
</para>
<para>
Like <function>LIKE</function>, the <function>SIMILAR TO</function>
operator succeeds only if its pattern matches the entire string;
this is unlike common regular expression practice, wherein the pattern
may match any part of the string.
Also like
<function>LIKE</function>, <function>SIMILAR TO</function> uses
<literal>%</> and <literal>_</> as wildcard characters denoting
any string and any single character, respectively (these are
comparable to <literal>.*</> and <literal>.</> in POSIX regular
expressions).
</para>
<para>
In addition to these facilities borrowed from <function>LIKE</function>,
<function>SIMILAR TO</function> supports these pattern-matching
metacharacters borrowed from POSIX regular expressions:
<itemizedlist>
<listitem>
<para>
<literal>|</literal> denotes alternation (either of two alternatives).
</para>
</listitem>
<listitem>
<para>
<literal>*</literal> denotes repetition of the previous item zero
or more times.
</para>
</listitem>
<listitem>
<para>
<literal>+</literal> denotes repetition of the previous item one
or more times.
</para>
</listitem>
<listitem>
<para>
Parentheses <literal>()</literal> may be used to group items into
a single logical item.
</para>
</listitem>
<listitem>
<para>
A bracket expression <literal>[...]</literal> specifies a character
class, just as in POSIX regular expressions.
</para>
</listitem>
</itemizedlist>
Notice that bounded repetition (<literal>?</> and <literal>{...}</>)
are not provided, though they exist in POSIX. Also, dot (<literal>.</>)
is not a metacharacter.
</para>
<para>
As with <function>LIKE</>, a backslash disables the special meaning
of any of these metacharacters; or a different escape character can
be specified with <literal>ESCAPE</>.
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
Some examples:
<programlisting>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
'abc' SIMILAR TO 'abc' <lineannotation>true</lineannotation>
'abc' SIMILAR TO 'a' <lineannotation>false</lineannotation>
'abc' SIMILAR TO '%(b|d)%' <lineannotation>true</lineannotation>
'abc' SIMILAR TO '(b|c)%' <lineannotation>false</lineannotation>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</programlisting>
</para>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The <function>SUBSTRING</> function with three parameters,
<function>SUBSTRING(<parameter>string</parameter> FROM
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<replaceable>pattern</replaceable> FOR
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<replaceable>escape</replaceable>)</function>, provides
extraction of a substring that matches a SQL99 regular expression
pattern. As with <literal>SIMILAR TO</>, the specified pattern
must match to the entire data string, else the function fails and
returns null. To indicate the part of the pattern that should be
returned on success, SQL99 specifies that the pattern must
contain two occurrences of the escape character followed by
double quote (<literal>"</>). The text matching the portion of
the pattern between these markers is returned.
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
Some examples:
<programlisting>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
SUBSTRING('foobar' FROM '%#"o_b#"%' FOR '#') <lineannotation>oob</lineannotation>
SUBSTRING('foobar' FROM '#"o_b#"%' FOR '#') <lineannotation>NULL</lineannotation>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</programlisting>
</para>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
</sect2>
<sect2 id="functions-posix-regexp">
<title><acronym>POSIX</acronym> Regular Expressions</title>
<indexterm zone="functions-posix-regexp">
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<primary>regular expressions</primary>
<seealso>pattern matching</seealso>
</indexterm>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="functions-posix-table"> lists the available
operators for pattern matching using POSIX regular expressions.
</para>
<table id="functions-posix-table">
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<title>Regular Expression Match Operators</title>
<tgroup cols="3">
<thead>
<row>
<entry>Operator</entry>
<entry>Description</entry>
<entry>Example</entry>
</row>
</thead>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<tbody>
<row>
<entry> <literal>~</literal> </entry>
<entry>Matches regular expression, case sensitive</entry>
<entry><literal>'thomas' ~ '.*thomas.*'</literal></entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> <literal>~*</literal> </entry>
<entry>Matches regular expression, case insensitive</entry>
<entry><literal>'thomas' ~* '.*Thomas.*'</literal></entry>
</row>
A little wordsmithing in the pattern-matching section.
2000-12-16 20:33:23 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row>
<entry> <literal>!~</literal> </entry>
<entry>Does not match regular expression, case sensitive</entry>
<entry><literal>'thomas' !~ '.*Thomas.*'</literal></entry>
</row>
<row>
<entry> <literal>!~*</literal> </entry>
<entry>Does not match regular expression, case insensitive</entry>
<entry><literal>'thomas' !~* '.*vadim.*'</literal></entry>
</row>
</tbody>
</tgroup>
</table>
<para>
<acronym>POSIX</acronym> regular expressions provide a more
powerful means for
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
pattern matching than the <function>LIKE</function> and
<function>SIMILAR TO</> operators.
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
Many Unix tools such as <command>egrep</command>,
<command>sed</command>, or <command>awk</command> use a pattern
matching language that is similar to the one described here.
</para>
<para>
A regular expression is a character sequence that is an
abbreviated definition of a set of strings (a <firstterm>regular
set</firstterm>). A string is said to match a regular expression
if it is a member of the regular set described by the regular
expression. As with <function>LIKE</function>, pattern characters
match string characters exactly unless they are special characters
in the regular expression language --- but regular expressions use
different special characters than <function>LIKE</function> does.
Unlike <function>LIKE</function> patterns, a
regular expression is allowed to match anywhere within a string, unless
the regular expression is explicitly anchored to the beginning or
end of the string.
</para>
A little wordsmithing in the pattern-matching section.
2000-12-16 20:33:23 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
Some examples:
<programlisting>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
'abc' ~ 'abc' <lineannotation>true</lineannotation>
'abc' ~ '^a' <lineannotation>true</lineannotation>
'abc' ~ '(b|d)' <lineannotation>true</lineannotation>
'abc' ~ '^(b|c)' <lineannotation>false</lineannotation>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</programlisting>
</para>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The <function>SUBSTRING</> function with two parameters,
<function>SUBSTRING(<parameter>string</parameter> FROM
<replaceable>pattern</replaceable>)</function>, provides extraction of a substring
that matches a POSIX regular expression pattern. It returns null if
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
there is no match, otherwise the portion of the text that matched the
pattern. But if the pattern contains any parentheses, the portion
of the text that matched the first parenthesized subexpression (the
one whose left parenthesis comes first) is
returned. You can always put parentheses around the whole expression
if you want to use parentheses within it without triggering this
exception.
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
Some examples:
<programlisting>
Bring SIMILAR TO and SUBSTRING into some semblance of conformance with the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
2002-09-22 19:27:25 +02:00
SUBSTRING('foobar' FROM 'o.b') <lineannotation>oob</lineannotation>
SUBSTRING('foobar' FROM 'o(.)b') <lineannotation>o</lineannotation>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</programlisting>
</para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<!-- derived from the re_format.7 man page -->
Minor updates for release.
1999-06-14 09:36:12 +02:00
<para>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
Regular expressions (<acronym>RE</acronym>s), as defined in
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<acronym>POSIX</acronym>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
1003.2, come in two forms: modern <acronym>RE</acronym>s (roughly those of
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<command>egrep</command>; 1003.2 calls these
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<quote>extended</quote> <acronym>RE</acronym>s) and obsolete <acronym>RE</acronym>s (roughly those of
<command>ed</command>; 1003.2 <quote>basic</quote> <acronym>RE</acronym>s).
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> implements the modern form.
Minor updates for release.
1999-06-14 09:36:12 +02:00
</para>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Minor updates for release.
1999-06-14 09:36:12 +02:00
<para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
A (modern) RE is one or more non-empty
<firstterm>branches</firstterm>, separated by
<literal>|</literal>. It matches anything that matches one of the
branches.
Minor updates for release.
1999-06-14 09:36:12 +02:00
</para>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +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
<para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
A branch is one or more <firstterm>pieces</firstterm>,
concatenated. It matches a match for the first, followed by a
match for the second, etc.
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>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
* to_char: - full support for IW (ISO week) and vice versa conversion for IW too (the to_char 'week' support is now complete and I hope correct). Thomas, I use for IW code from timestamp.c, for this I create separate function date2isoweek() from original 'case DTK_WEEK:' code in the timestamp_part(). I mean will better use one code for same feature in date_part() and in to_char(). The isoweek2date() is added to timestamp.c too. Right? IMHO in 7.1 will all to_char's features complete. It is cca 41 templates for date/time and cca 21 for numbers. * to_ascii: - gcc, is it correct now? :-) In the patch is documentation for to_char's IW and for to_ascii(). Karel
2000-08-29 06:41:48 +02:00
<para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
A piece is an <firstterm>atom</firstterm> possibly followed by a
single <literal>*</literal>, <literal>+</literal>,
<literal>?</literal>, or <firstterm>bound</firstterm>. An atom
followed by <literal>*</literal> matches a sequence of 0 or more
matches of the atom. An atom followed by <literal>+</literal>
matches a sequence of 1 or more matches of the atom. An atom
followed by <literal>?</literal> matches a sequence of 0 or 1
matches of the atom.
* to_char: - full support for IW (ISO week) and vice versa conversion for IW too (the to_char 'week' support is now complete and I hope correct). Thomas, I use for IW code from timestamp.c, for this I create separate function date2isoweek() from original 'case DTK_WEEK:' code in the timestamp_part(). I mean will better use one code for same feature in date_part() and in to_char(). The isoweek2date() is added to timestamp.c too. Right? IMHO in 7.1 will all to_char's features complete. It is cca 41 templates for date/time and cca 21 for numbers. * to_ascii: - gcc, is it correct now? :-) In the patch is documentation for to_char's IW and for to_ascii(). Karel
2000-08-29 06:41:48 +02:00
</para>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<para>
A <firstterm>bound</firstterm> is <literal>{</literal> followed by
an unsigned decimal integer, possibly followed by
<literal>,</literal> possibly followed by another unsigned decimal
integer, always followed by <literal>}</literal>. The integers
must lie between 0 and <symbol>RE_DUP_MAX</symbol> (255)
inclusive, and if there are two of them, the first may not exceed
the second. An atom followed by a bound containing one integer
<replaceable>i</replaceable> and no comma matches a sequence of
exactly <replaceable>i</replaceable> matches of the atom. An atom
followed by a bound containing one integer
<replaceable>i</replaceable> and a comma matches a sequence of
<replaceable>i</replaceable> or more matches of the atom. An atom
followed by a bound containing two integers
<replaceable>i</replaceable> and <replaceable>j</replaceable>
matches a sequence of <replaceable>i</replaceable> through
<replaceable>j</replaceable> (inclusive) matches of the atom.
</para>
<note>
<para>
A repetition operator (<literal>?</literal>,
<literal>*</literal>, <literal>+</literal>, or bounds) cannot
follow another repetition operator. A repetition operator cannot
begin an expression or subexpression or follow
<literal>^</literal> or <literal>|</literal>.
</para>
</note>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +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
<para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
An <firstterm>atom</firstterm> is a regular expression enclosed in
<literal>()</literal> (matching a match for the regular
expression), an empty set of <literal>()</literal> (matching the
null string), a <firstterm>bracket expression</firstterm> (see
below), <literal>.</literal> (matching any single character),
The regexp pattern characters ^ and $ should be explained as matching at the beginning and end of the input string, not the beginning and end of "a line", since Postgres does not allow them to match at newline characters in the data.
2001-03-25 20:14:31 +02:00
<literal>^</literal> (matching the null string at the beginning of the
input string), <literal>$</literal> (matching the null string at the end
of the input string), a <literal>\</literal> followed by one of the
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
characters <literal>^.[$()|*+?{\</literal> (matching that
character taken as an ordinary character), a <literal>\</literal>
followed by any other character (matching that character taken as
an ordinary character, as if the <literal>\</literal> had not been
present), or a single character with no other significance
(matching that character). A <literal>{</literal> followed by a
character other than a digit is an ordinary character, not the
beginning of a bound. It is illegal to end an RE with
<literal>\</literal>.
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>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
A little wordsmithing in the pattern-matching section.
2000-12-16 20:33:23 +01:00
<para>
Note that the backslash (<literal>\</literal>) already has a special
meaning in string
literals, so to write a pattern constant that contains a backslash
you must write two backslashes in the query.
</para>
Minor updates for release.
1999-06-14 09:36:12 +02:00
<para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
A <firstterm>bracket expression</firstterm> is a list of
characters enclosed in <literal>[]</literal>. It normally matches
any single character from the list (but see below). If the list
begins with <literal>^</literal>, it matches any single character
(but see below) not from the rest of the list. If two characters
in the list are separated by <literal>-</literal>, this is
shorthand for the full range of characters between those two
(inclusive) in the collating sequence,
e.g. <literal>[0-9]</literal> in <acronym>ASCII</acronym> matches
any decimal digit. It is illegal for two ranges to share an
endpoint, e.g. <literal>a-c-e</literal>. Ranges are very
collating-sequence-dependent, and portable programs should avoid
relying on them.
Minor updates for release.
1999-06-14 09:36:12 +02:00
</para>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Minor updates for release.
1999-06-14 09:36:12 +02:00
<para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
To include a literal <literal>]</literal> in the list, make it the
first character (following a possible <literal>^</literal>). To
include a literal <literal>-</literal>, make it the first or last
character, or the second endpoint of a range. To use a literal
<literal>-</literal> as the first endpoint of a range, enclose it
in <literal>[.</literal> and <literal>.]</literal> to make it a
collating element (see below). With the exception of these and
some combinations using <literal>[</literal> (see next
paragraphs), all other special characters, including
<literal>\</literal>, lose their special significance within a
bracket expression.
</para>
<para>
Within a bracket expression, a collating element (a character, a
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
multiple-character sequence that collates as if it were a single
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
character, or a collating-sequence name for either) enclosed in
<literal>[.</literal> and <literal>.]</literal> stands for the
sequence of characters of that collating element. The sequence is
a single element of the bracket expression's list. A bracket
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
expression containing a multiple-character collating element can thus
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
match more than one character, e.g. if the collating sequence
includes a <literal>ch</literal> collating element, then the RE
<literal>[[.ch.]]*c</literal> matches the first five characters of
<literal>chchcc</literal>.
</para>
<para>
Within a bracket expression, a collating element enclosed in
<literal>[=</literal> and <literal>=]</literal> is an equivalence
class, standing for the sequences of characters of all collating
elements equivalent to that one, including itself. (If there are
no other equivalent collating elements, the treatment is as if the
enclosing delimiters were <literal>[.</literal> and
<literal>.]</literal>.) For example, if <literal>o</literal> and
<literal>^</literal> are the members of an equivalence class, then
<literal>[[=o=]]</literal>, <literal>[[=^=]]</literal>, and
<literal>[o^]</literal> are all synonymous. An equivalence class
may not be an endpoint of a range.
</para>
<para>
Within a bracket expression, the name of a character class
enclosed in <literal>[:</literal> and <literal>:]</literal> stands
for the list of all characters belonging to that class. Standard
character class names are: <literal>alnum</literal>,
<literal>alpha</literal>, <literal>blank</literal>,
<literal>cntrl</literal>, <literal>digit</literal>,
<literal>graph</literal>, <literal>lower</literal>,
<literal>print</literal>, <literal>punct</literal>,
<literal>space</literal>, <literal>upper</literal>,
<literal>xdigit</literal>. These stand for the character classes
defined in
<citerefentry><refentrytitle>ctype</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
A locale may provide others. A character class may not be used as
an endpoint of a range.
</para>
<para>
There are two special cases of bracket expressions: the bracket
Add more documentation about CURRENT_TIMESTAMP. Also, code < and > as &lt;/&gt; for cleaner SGML.
2002-10-05 21:03:16 +02:00
expressions <literal>[[:&lt;:]]</literal> and
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<literal>[[:>:]]</literal> match the null string at the beginning
and end of a word respectively. A word is defined as a sequence
of word characters which is neither preceded nor followed by word
characters. A word character is an alnum character (as defined by
<citerefentry><refentrytitle>ctype</refentrytitle><manvolnum>3</manvolnum></citerefentry>)
or an underscore. This is an extension, compatible with but not
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
specified by <acronym>POSIX</acronym> 1003.2, and should be used with caution in
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
software intended to be portable to other systems.
</para>
<para>
In the event that an RE could match more than one substring of a
given string, the RE matches the one starting earliest in the
string. If the RE could match more than one substring starting at
that point, it matches the longest. Subexpressions also match the
longest possible substrings, subject to the constraint that the
whole match be as long as possible, with subexpressions starting
earlier in the RE taking priority over ones starting later. Note
that higher-level subexpressions thus take priority over their
lower-level component subexpressions.
</para>
<para>
Match lengths are measured in characters, not collating
elements. A null string is considered longer than no match at
all. For example, <literal>bb*</literal> matches the three middle
characters of <literal>abbbc</literal>,
<literal>(wee|week)(knights|nights)</literal> matches all ten
characters of <literal>weeknights</literal>, when
<literal>(.*).*</literal> is matched against
<literal>abc</literal> the parenthesized subexpression matches all
three characters, and when <literal>(a*)*</literal> is matched
against <literal>bc</literal> both the whole RE and the
parenthesized subexpression match the null string.
</para>
<para>
If case-independent matching is specified, the effect is much as
if all case distinctions had vanished from the alphabet. When an
alphabetic that exists in multiple cases appears as an ordinary
character outside a bracket expression, it is effectively
transformed into a bracket expression containing both cases,
e.g. <literal>x</literal> becomes <literal>[xX]</literal>. When
it appears inside a bracket expression, all case counterparts of
it are added to the bracket expression, so that (e.g.)
<literal>[x]</literal> becomes <literal>[xX]</literal> and
<literal>[^x]</literal> becomes <literal>[^xX]</literal>.
</para>
<para>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
There is no particular limit on the length of <acronym>RE</acronym>s, except insofar
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
as memory is limited. Memory usage is approximately linear in RE
size, and largely insensitive to RE complexity, except for bounded
repetitions. Bounded repetitions are implemented by macro
expansion, which is costly in time and space if counts are large
or bounded repetitions are nested. An RE like, say,
<literal>((((a{1,100}){1,100}){1,100}){1,100}){1,100}</literal>
will (eventually) run almost any existing machine out of swap
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
space.
<footnote>
<para>
This was written in 1994, mind you. The
numbers have probably changed, but the problem
persists.
</para>
</footnote>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<!-- end re_format.7 man page -->
</sect2>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</sect1>
<sect1 id="functions-formatting">
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
<title>Data Type Formatting Functions</title>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +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="functions-formatting">
<primary>formatting</primary>
</indexterm>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01: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 <productname>PostgreSQL</productname> formatting functions
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
provide a powerful set of tools for converting various data types
(date/time, integer, floating point, numeric) to formatted strings
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
and for converting from formatted strings to specific data types.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<xref linkend="functions-formatting-table"> lists them.
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
These functions all follow a common calling convention: the first
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
argument is the value to be formatted and the second argument is a
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
template that defines the output or input format.
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table id="functions-formatting-table">
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<title>Formatting Functions</title>
<tgroup cols="4">
<thead>
<row>
<entry>Function</entry>
<entry>Returns</entry>
<entry>Description</entry>
<entry>Example</entry>
</row>
</thead>
<tbody>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>to_char</function>(<type>timestamp</type>, <type>text</type>)</entry>
<entry><type>text</type></entry>
<entry>convert time stamp to string</entry>
<entry><literal>to_char(timestamp 'now','HH12:MI:SS')</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
- new to_char(interval, text) - new millisecond (ms) and microsecond (us) support - more robus parsing from string - used is separator checking for non-exact formats like to_date('2001-9-1', 'YYYY-MM-DD') - SGML docs are included Karel Zak
2001-09-06 05:22:42 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>to_char</function>(<type>interval</type>, <type>text</type>)</entry>
<entry><type>text</type></entry>
- new to_char(interval, text) - new millisecond (ms) and microsecond (us) support - more robus parsing from string - used is separator checking for non-exact formats like to_date('2001-9-1', 'YYYY-MM-DD') - SGML docs are included Karel Zak
2001-09-06 05:22:42 +02:00
<entry>convert interval to string</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(interval '15h 2m 12s','HH24:MI:SS')</literal></entry>
- new to_char(interval, text) - new millisecond (ms) and microsecond (us) support - more robus parsing from string - used is separator checking for non-exact formats like to_date('2001-9-1', 'YYYY-MM-DD') - SGML docs are included Karel Zak
2001-09-06 05:22:42 +02:00
</row>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>to_char</function>(<type>int</type>, <type>text</type>)</entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>convert integer to string</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(125, '999')</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>to_char</function>(<type>double precision</type>,
<type>text</type>)</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>text</type></entry>
Replace some oldish, non-SQL'ish elements with more standard forms. (cast syntax, type names, function names, etc.)
2001-01-20 21:59:29 +01:00
<entry>convert real/double precision to string</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(125.8, '999D9')</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>to_char</function>(<type>numeric</type>, <type>text</type>)</entry>
<entry><type>text</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>convert numeric to string</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(numeric '-125.8', '999D99S')</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>to_date</function>(<type>text</type>, <type>text</type>)</entry>
<entry><type>date</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>convert string to date</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_date('05 Dec 2000', 'DD Mon YYYY')</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>to_timestamp</function>(<type>text</type>, <type>text</type>)</entry>
<entry><type>timestamp</type></entry>
<entry>convert string to time stamp</entry>
<entry><literal>to_timestamp('05 Dec 2000', 'DD Mon YYYY')</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>to_number</function>(<type>text</type>, <type>text</type>)</entry>
<entry><type>numeric</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>convert string to numeric</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_number('12,454.8-', '99G999D9S')</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
</tbody>
</tgroup>
</table>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<para>
In an output template string, there are certain patterns that are
recognized and replaced with appropriately-formatted data from the value
to be formatted. Any text that is not a template pattern is simply
proof-reading
2001-11-28 21:49:10 +01:00
copied verbatim. Similarly, in an input template string, template patterns
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
identify the parts of the input data string to be looked at and the
values to be found there.
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="functions-formatting-datetime-table"> shows the
template patterns available for formatting date and time values.
</para>
<table id="functions-formatting-datetime-table">
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<title>Template patterns for date/time conversions</title>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<tgroup cols="2">
<thead>
<row>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry>Pattern</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01: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><literal>HH</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>hour of day (01-12)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>HH12</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>hour of day (01-12)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>HH24</literal></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>hour of day (00-23)</entry>
</row>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>MI</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>minute (00-59)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>SS</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>second (00-59)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
- new to_char(interval, text) - new millisecond (ms) and microsecond (us) support - more robus parsing from string - used is separator checking for non-exact formats like to_date('2001-9-1', 'YYYY-MM-DD') - SGML docs are included Karel Zak
2001-09-06 05:22:42 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>MS</literal></entry>
- new to_char(interval, text) - new millisecond (ms) and microsecond (us) support - more robus parsing from string - used is separator checking for non-exact formats like to_date('2001-9-1', 'YYYY-MM-DD') - SGML docs are included Karel Zak
2001-09-06 05:22:42 +02:00
<entry>millisecond (000-999)</entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>US</literal></entry>
- new to_char(interval, text) - new millisecond (ms) and microsecond (us) support - more robus parsing from string - used is separator checking for non-exact formats like to_date('2001-9-1', 'YYYY-MM-DD') - SGML docs are included Karel Zak
2001-09-06 05:22:42 +02:00
<entry>microsecond (000000-999999)</entry>
</row>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>SSSS</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>seconds past midnight (0-86399)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
Update create_rule manual page.
2000-04-07 21:17:51 +02:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>AM</literal> or <literal>A.M.</literal> or
A few more fixes for the <replaceable>able> fiasco.
2002-08-29 07:17:55 +02:00
<literal>PM</literal> or <literal>P.M.</literal></entry>
Update create_rule manual page.
2000-04-07 21:17:51 +02:00
<entry>meridian indicator (upper case)</entry>
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>am</literal> or <literal>a.m.</literal> or
A few more fixes for the <replaceable>able> fiasco.
2002-08-29 07:17:55 +02:00
<literal>pm</literal> or <literal>p.m.</literal></entry>
Update create_rule manual page.
2000-04-07 21:17:51 +02:00
<entry>meridian indicator (lower case)</entry>
</row>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>Y,YYY</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>year (4 and more digits) with comma</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>YYYY</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>year (4 and more digits)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>YYY</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>last 3 digits of year</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>YY</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>last 2 digits of year</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>Y</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>last digit of year</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
Update create_rule manual page.
2000-04-07 21:17:51 +02:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>BC</literal> or <literal>B.C.</literal> or
A few more fixes for the <replaceable>able> fiasco.
2002-08-29 07:17:55 +02:00
<literal>AD</literal> or <literal>A.D.</literal></entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry>era indicator (upper case)</entry>
Update create_rule manual page.
2000-04-07 21:17:51 +02:00
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal>bc</literal> or <literal>b.c.</literal> or
A few more fixes for the <replaceable>able> fiasco.
2002-08-29 07:17:55 +02:00
<literal>ad</literal> or <literal>a.d.</literal></entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry>era indicator (lower case)</entry>
Update create_rule manual page.
2000-04-07 21:17:51 +02:00
</row>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>MONTH</literal></entry>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry>full upper case month name (blank-padded to 9 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>Month</literal></entry>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry>full mixed case month name (blank-padded to 9 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>month</literal></entry>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry>full lower case month name (blank-padded to 9 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>MON</literal></entry>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry>abbreviated upper case month name (3 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>Mon</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>abbreviated mixed case month name (3 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>mon</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>abbreviated lower case month name (3 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>MM</literal></entry>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry>month number (01-12)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>DAY</literal></entry>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry>full upper case day name (blank-padded to 9 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>Day</literal></entry>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry>full mixed case day name (blank-padded to 9 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>day</literal></entry>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry>full lower case day name (blank-padded to 9 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>DY</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>abbreviated upper case day name (3 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>Dy</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>abbreviated mixed case day name (3 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>dy</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>abbreviated lower case day name (3 chars)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>DDD</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>day of year (001-366)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>DD</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>day of month (01-31)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>D</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>day of week (1-7; SUN=1)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>W</literal></entry>
In the attache is new (correct) version. I add TZ (timezone) support for to_char() too. Karel
2000-07-03 18:01:33 +02:00
<entry>week of month (1-5) where first week start on the first day of the month</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>WW</literal></entry>
In the attache is new (correct) version. I add TZ (timezone) support for to_char() too. Karel
2000-07-03 18:01:33 +02:00
<entry>week number of year (1-53) where first week start on the first day of the year</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
* to_char: - full support for IW (ISO week) and vice versa conversion for IW too (the to_char 'week' support is now complete and I hope correct). Thomas, I use for IW code from timestamp.c, for this I create separate function date2isoweek() from original 'case DTK_WEEK:' code in the timestamp_part(). I mean will better use one code for same feature in date_part() and in to_char(). The isoweek2date() is added to timestamp.c too. Right? IMHO in 7.1 will all to_char's features complete. It is cca 41 templates for date/time and cca 21 for numbers. * to_ascii: - gcc, is it correct now? :-) In the patch is documentation for to_char's IW and for to_ascii(). Karel
2000-08-29 06:41:48 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>IW</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>ISO week number of year (The first Thursday of the new year is in week 1.)</entry>
* to_char: - full support for IW (ISO week) and vice versa conversion for IW too (the to_char 'week' support is now complete and I hope correct). Thomas, I use for IW code from timestamp.c, for this I create separate function date2isoweek() from original 'case DTK_WEEK:' code in the timestamp_part(). I mean will better use one code for same feature in date_part() and in to_char(). The isoweek2date() is added to timestamp.c too. Right? IMHO in 7.1 will all to_char's features complete. It is cca 41 templates for date/time and cca 21 for numbers. * to_ascii: - gcc, is it correct now? :-) In the patch is documentation for to_char's IW and for to_ascii(). Karel
2000-08-29 06:41:48 +02:00
</row>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>CC</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>century (2 digits)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>J</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>Julian Day (days since January 1, 4712 BC)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>Q</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>quarter</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>RM</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>month in Roman Numerals (I-XII; I=January) - upper case</entry>
Update create_rule manual page.
2000-04-07 21:17:51 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>rm</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>month in Roman Numerals (I-XII; I=January) - lower case</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
In the attache is new (correct) version. I add TZ (timezone) support for to_char() too. Karel
2000-07-03 18:01:33 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>TZ</literal></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>time-zone name - upper case</entry>
In the attache is new (correct) version. I add TZ (timezone) support for to_char() too. Karel
2000-07-03 18:01:33 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>tz</literal></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>time-zone name - lower case</entry>
In the attache is new (correct) version. I add TZ (timezone) support for to_char() too. Karel
2000-07-03 18:01:33 +02:00
</row>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</tbody>
</tgroup>
</table>
<para>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
Certain modifiers may be applied to any template pattern to alter its
behavior. For example, <quote><literal>FMMonth</literal></quote>
is the <quote><literal>Month</literal></quote> pattern with the
<quote><literal>FM</literal></quote> prefix.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<xref linkend="functions-formatting-datetimemod-table"> shows the
modifier patterns for date/time formatting.
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table id="functions-formatting-datetimemod-table">
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<title>Template pattern modifiers for date/time conversions</title>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<tgroup cols="3">
<thead>
<row>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry>Modifier</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<entry>Description</entry>
<entry>Example</entry>
</row>
</thead>
<tbody>
<row>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry><literal>FM</literal> prefix</entry>
<entry>fill mode (suppress padding blanks and zeroes)</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>FMMonth</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry><literal>TH</literal> suffix</entry>
<entry>add upper-case ordinal number suffix</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>DDTH</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry><literal>th</literal> suffix</entry>
<entry>add lower-case ordinal number suffix</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>DDth</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry><literal>FX</literal> prefix</entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>fixed format global option (see usage notes)</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>FX Month DD Day</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry><literal>SP</literal> suffix</entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>spell mode (not yet implemented)</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>DDSP</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
</tbody>
</tgroup>
</table>
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Usage notes for the date/time formatting:
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<itemizedlist>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<listitem>
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<literal>FM</literal> suppresses leading zeroes and trailing blanks
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
that would otherwise be added to make the output of a pattern be
fixed-width.
</para>
</listitem>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<listitem>
<para>
<function>to_timestamp</function> and <function>to_date</function>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
skip multiple blank spaces in the input string if the <literal>FX</literal> option
In the attache is new (correct) version. I add TZ (timezone) support for to_char() too. Karel
2000-07-03 18:01:33 +02:00
is not used. <literal>FX</literal> must be specified as the first item
in the template; for example
<literal>to_timestamp('2000 JUN','YYYY MON')</literal> is right, but
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<literal>to_timestamp('2000 JUN','FXYYYY MON')</literal> returns an error,
because <function>to_timestamp</function> expects one blank space only.
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
</para>
</listitem>
<listitem>
<para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
If a backslash (<quote><literal>\</literal></quote>) is desired
in a string constant, a double backslash
(<quote><literal>\\</literal></quote>) must be entered; for
example <literal>'\\HH\\MI\\SS'</literal>. This is true for
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
any string constant in <productname>PostgreSQL</productname>.
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
</para>
</listitem>
<listitem>
<para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Ordinary text is allowed in <function>to_char</function>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
templates and will be output literally. You can put a substring
in double quotes to force it to be interpreted as literal text
even if it contains pattern keywords. For example, in
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<literal>'"Hello Year "YYYY'</literal>, the <literal>YYYY</literal>
will be replaced by the year data, but the single <literal>Y</literal> in <quote>Year</quote>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
will not be.
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
</para>
</listitem>
<listitem>
<para>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
If you want to have a double quote in the output you must
precede it with a backslash, for example <literal>'\\"YYYY
Month\\"'</literal>. <!-- "" font-lock sanity :-) -->
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
</para>
</listitem>
here is a patch for formatting.c (to_char/timestampt()), for 7.1 it fixing Y,YY,YYY,YYYY conversion, the docs and regress tests update are included too. During the patch testing I found small bug in miscadmin.h in convertstr() declaration. Here it's fixed too. Thanks Karel
2000-11-25 06:00:33 +01:00
<listitem>
<para>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<literal>YYYY</literal> conversion from string to <type>timestamp</type> or
<type>date</type> is restricted if you use a year with more than 4 digits. You must
Repair markup
2000-11-25 14:20:05 +01:00
use some non-digit character or template after <literal>YYYY</literal>,
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
otherwise the year is always interpreted as 4 digits. For example
Repair markup
2000-11-25 14:20:05 +01:00
(with year 20000):
<literal>to_date('200001131', 'YYYYMMDD')</literal> will be
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
interpreted as a 4-digit year; better is to use a non-digit
Repair markup
2000-11-25 14:20:05 +01:00
separator after the year, like
<literal>to_date('20000-1131', 'YYYY-MMDD')</literal> or
<literal>to_date('20000Nov31', 'YYYYMonDD')</literal>.
here is a patch for formatting.c (to_char/timestampt()), for 7.1 it fixing Y,YY,YYY,YYYY conversion, the docs and regress tests update are included too. During the patch testing I found small bug in miscadmin.h in convertstr() declaration. Here it's fixed too. Thanks Karel
2000-11-25 06:00:33 +01:00
</para>
</listitem>
- new to_char(interval, text) - new millisecond (ms) and microsecond (us) support - more robus parsing from string - used is separator checking for non-exact formats like to_date('2001-9-1', 'YYYY-MM-DD') - SGML docs are included Karel Zak
2001-09-06 05:22:42 +02:00
<listitem>
<para>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
Millisecond <literal>MS</literal> and microsecond <literal>US</literal>
proof-reading
2001-11-28 21:49:10 +01:00
values in a conversion from string to time stamp are used as part of the
seconds after the decimal point. For example
- new to_char(interval, text) - new millisecond (ms) and microsecond (us) support - more robus parsing from string - used is separator checking for non-exact formats like to_date('2001-9-1', 'YYYY-MM-DD') - SGML docs are included Karel Zak
2001-09-06 05:22:42 +02:00
<literal>to_timestamp('12:3', 'SS:MS')</literal> is not 3 milliseconds,
proof-reading
2001-11-28 21:49:10 +01:00
but 300, because the conversion counts it as 12 + 0.3.
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
This means for the format <literal>SS:MS</literal>, the input values
<literal>12:3</literal>, <literal>12:30</literal>, and <literal>12:300</literal> specify the
proof-reading
2001-11-28 21:49:10 +01:00
same number of milliseconds. To get three milliseconds, one must use
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<literal>12:003</literal>, which the conversion counts as
proof-reading
2001-11-28 21:49:10 +01:00
12 + 0.003 = 12.003 seconds.
</para>
<para>
Here is a more
- new to_char(interval, text) - new millisecond (ms) and microsecond (us) support - more robus parsing from string - used is separator checking for non-exact formats like to_date('2001-9-1', 'YYYY-MM-DD') - SGML docs are included Karel Zak
2001-09-06 05:22:42 +02:00
complex example:
<literal>to_timestamp('15:12:02.020.001230','HH:MI:SS.MS.US')</literal>
proof-reading
2001-11-28 21:49:10 +01:00
is 15 hours, 12 minutes, and 2 seconds + 20 milliseconds +
1230 microseconds = 2.021230 seconds.
- new to_char(interval, text) - new millisecond (ms) and microsecond (us) support - more robus parsing from string - used is separator checking for non-exact formats like to_date('2001-9-1', 'YYYY-MM-DD') - SGML docs are included Karel Zak
2001-09-06 05:22:42 +02:00
</para>
</listitem>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
</itemizedlist>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</para>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="functions-formatting-numeric-table"> shows the
template patterns available for formatting numeric values.
</para>
<table id="functions-formatting-numeric-table">
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<title>Template patterns for numeric conversions</title>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<tgroup cols="2">
<thead>
<row>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry>Pattern</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01: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><literal>9</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>value with the specified number of digits</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>0</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>value with leading zeros</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>.</literal> (period)</entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>decimal point</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>,</literal> (comma)</entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>group (thousand) separator</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>PR</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>negative value in angle brackets</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>S</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>negative value with minus sign (uses locale)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>L</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>currency symbol (uses locale)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>D</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>decimal point (uses locale)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>G</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>group separator (uses locale)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>MI</literal></entry>
Add more documentation about CURRENT_TIMESTAMP. Also, code < and > as &lt;/&gt; for cleaner SGML.
2002-10-05 21:03:16 +02:00
<entry>minus sign in specified position (if number &lt; 0)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>PL</literal></entry>
Add more documentation about CURRENT_TIMESTAMP. Also, code < and > as &lt;/&gt; for cleaner SGML.
2002-10-05 21:03:16 +02:00
<entry>plus sign in specified position (if number &gt; 0)</entry>
I'm sending patch with new version of to_char numbers formatting. The PostgreSQL's to_char() is very compatible with Oracle's to_char now. I hope that to_char's 3000 rows of source is without bugs, but will good if anyone test it, for me it works very well :-) Karel ---------------------------------------------------------------------- Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-02-08 16:57:01 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>SG</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>plus/minus sign in specified position</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>RN</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>roman numeral (input between 1 and 3999)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>TH</literal> or <literal>th</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>convert to ordinal number</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>V</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>shift <replaceable>n</replaceable> digits (see
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
notes)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>EEEE</literal></entry>
proof-reading
2001-11-28 21:49:10 +01:00
<entry>scientific notation (not implemented yet)</entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
</tbody>
</tgroup>
</table>
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Usage notes for the numeric formatting:
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<itemizedlist>
<listitem>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
A sign formatted using <literal>SG</literal>, <literal>PL</literal>, or
<literal>MI</literal> is not an anchor in
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
the number; for example,
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<literal>to_char(-12, 'S9999')</literal> produces <literal>' -12'</literal>,
but <literal>to_char(-12, 'MI9999')</literal> produces <literal>'- 12'</literal>.
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
The Oracle implementation does not allow the use of
<literal>MI</literal> ahead of <literal>9</literal>, but rather
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
requires that <literal>9</literal> precede
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<literal>MI</literal>.
</para>
</listitem>
<listitem>
<para>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<literal>9</literal> specifies a value with the same number of
digits as there are <literal>9</literal>s. If a digit is
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
not available it outputs a space.
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
</para>
</listitem>
<listitem>
<para>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<literal>TH</literal> does not convert values less than zero
and does not convert decimal numbers.
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
</para>
</listitem>
<listitem>
<para>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<literal>PL</literal>, <literal>SG</literal>, and
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>TH</literal> are <productname>PostgreSQL</productname>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
extensions.
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
</para>
</listitem>
<listitem>
<para>
<literal>V</literal> effectively
multiplies the input values by
<literal>10^<replaceable>n</replaceable></literal>, where
<replaceable>n</replaceable> is the number of digits following
<literal>V</literal>.
<function>to_char</function> does not support the use of
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<literal>V</literal> combined with a decimal point.
(E.g., <literal>99.9V99</literal> is not allowed.)
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
</para>
</listitem>
</itemizedlist>
I'm sending patch with new version of to_char numbers formatting. The PostgreSQL's to_char() is very compatible with Oracle's to_char now. I hope that to_char's 3000 rows of source is without bugs, but will good if anyone test it, for me it works very well :-) Karel ---------------------------------------------------------------------- Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-02-08 16:57:01 +01:00
</para>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="functions-formatting-examples-table"> shows some
examples of the use of the <function>to_char</function> function.
</para>
<table id="functions-formatting-examples-table">
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<title><function>to_char</function> Examples</title>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<tgroup cols="2">
<thead>
<row>
<entry>Input</entry>
<entry>Output</entry>
</row>
</thead>
<tbody>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(now(),'Day, DD HH12:MI:SS')</literal></entry>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry><literal>'Tuesday , 06 05:39:18'</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
</row>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(now(),'FMDay, FMDD HH12:MI:SS')</literal></entry>
Improve description of to_char templates.
2001-03-15 02:07:51 +01:00
<entry><literal>'Tuesday, 6 05:39:18'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(-0.1,'99.99')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' -.10'</literal></entry>
I'm sending patch with new version of to_char numbers formatting. The PostgreSQL's to_char() is very compatible with Oracle's to_char now. I hope that to_char's 3000 rows of source is without bugs, but will good if anyone test it, for me it works very well :-) Karel ---------------------------------------------------------------------- Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-02-08 16:57:01 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(-0.1,'FM9.99')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'-.1'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(0.1,'0.9')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 0.1'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(12,'9990999.9')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 0012.0'</literal></entry>
I'm sending patch with new version of to_char numbers formatting. The PostgreSQL's to_char() is very compatible with Oracle's to_char now. I hope that to_char's 3000 rows of source is without bugs, but will good if anyone test it, for me it works very well :-) Karel ---------------------------------------------------------------------- Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-02-08 16:57:01 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(12,'FM9990999.9')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'0012'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(485,'999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 485'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(-485,'999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'-485'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(485,'9 9 9')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 4 8 5'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(1485,'9,999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 1,485'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(1485,'9G999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 1 485'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(148.5,'999.999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 148.500'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(148.5,'999D999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 148,500'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(3148.5,'9G999D999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 3 148,500'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(-485,'999S')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'485-'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(-485,'999MI')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'485-'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(485,'999MI')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'485'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(485,'PL999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'+485'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(485,'SG999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'+485'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(-485,'SG999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'-485'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(-485,'9SG99')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'4-85'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(-485,'999PR')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'&lt;485&gt;'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(485,'L999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'DM 485</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(485,'RN')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' CDLXXXV'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(485,'FMRN')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'CDLXXXV'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(5.2,'FMRN')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>V</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(482,'999th')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 482nd'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(485, '"Good number:"999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>'Good number: 485'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(485.8,'"Pre:"999" Post:" .999')</literal></entry>
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
<entry><literal>'Pre: 485 Post: .800'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(12,'99V999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 12000'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(12.4,'99V999')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 12400'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>to_char(12.45, '99V9')</literal></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry><literal>' 125'</literal></entry>
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</row>
</tbody>
</tgroup>
</table>
Don't put empty paragraphs around tables. This messed up JadeTeX somehow, and doesn't make sense strictly speaking.
2002-01-30 22:55:33 +01:00
as attache of this mail is patch (to the main tree) with to_char's family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
2000-01-26 00:53:56 +01:00
</sect1>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<sect1 id="functions-datetime">
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
<title>Date/Time Functions and Operators</title>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="functions-datetime-table"> shows the available
functions for date/time value processing, with details appearing in
the following subsections. <xref
linkend="operators-datetime-table"> illustrates the behaviors of
the basic arithmetic operators (<literal>+</literal>,
<literal>*</literal>, etc.). For formatting functions, refer to
<xref linkend="functions-formatting">. You should be familiar with
the background information on date/time data types (see <xref
Fix breakage in new-in-7.3 timetz_zone() function: was giving random results due to doing arithmetic on uninitialized values. Add some documentation about the AT TIME ZONE construct. Update some other date/time documentation that seemed out of date for 7.3.
2002-11-22 00:31:20 +01:00
linkend="datatype-datetime">).
</para>
<para>
All the functions and operators described below that take time or timestamp
inputs actually come in two variants: one that takes time or timestamp
with time zone, and one that takes time or timestamp without time zone.
For brevity, these variants are not shown separately.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</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
<table id="operators-datetime-table">
<title>Date/Time Operators</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="3">
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
<thead>
<row>
<entry>Name</entry>
<entry>Example</entry>
<entry>Result</entry>
</row>
</thead>
<tbody>
<row>
Fix markup to allow compilation. The chapters on failure and recovery need more work, but at least they have something now.
2001-09-28 22:48:17 +02:00
<entry> <literal>+</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>timestamp '2001-09-28 01:00' + interval '23 hours'</literal></entry>
<entry><literal>timestamp '2001-09-29 00:00'</literal></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
</row>
<row>
Fix markup to allow compilation. The chapters on failure and recovery need more work, but at least they have something now.
2001-09-28 22:48:17 +02:00
<entry> <literal>+</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>date '2001-09-28' + interval '1 hour'</literal></entry>
<entry><literal>timestamp '2001-09-28 01:00'</literal></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
</row>
<row>
Fix markup to allow compilation. The chapters on failure and recovery need more work, but at least they have something now.
2001-09-28 22:48:17 +02:00
<entry> <literal>+</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>time '01:00' + interval '3 hours'</literal></entry>
<entry><literal>time '04:00'</literal></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
</row>
<row>
Fix markup to allow compilation. The chapters on failure and recovery need more work, but at least they have something now.
2001-09-28 22:48:17 +02:00
<entry> <literal>-</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>timestamp '2001-09-28 23:00' - interval '23 hours'</literal></entry>
<entry><literal>timestamp '2001-09-28'</literal></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
</row>
<row>
Fix markup to allow compilation. The chapters on failure and recovery need more work, but at least they have something now.
2001-09-28 22:48:17 +02:00
<entry> <literal>-</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>date '2001-09-28' - interval '1 hour'</literal></entry>
<entry><literal>timestamp '2001-09-27 23:00'</literal></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
</row>
<row>
Fix markup to allow compilation. The chapters on failure and recovery need more work, but at least they have something now.
2001-09-28 22:48:17 +02:00
<entry> <literal>-</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>time '05:00' - interval '2 hours'</literal></entry>
<entry><literal>time '03:00'</literal></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
</row>
<row>
Fix markup to allow compilation. The chapters on failure and recovery need more work, but at least they have something now.
2001-09-28 22:48:17 +02:00
<entry> <literal>-</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>interval '2 hours' - time '05:00'</literal></entry>
<entry><literal>time '03:00:00'</literal></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
</row>
<row>
<entry> <literal>*</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>interval '1 hour' * int '3'</literal></entry>
<entry><literal>interval '03:00'</literal></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
</row>
<row>
<entry> <literal>/</literal> </entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><literal>interval '1 hour' / int '3'</literal></entry>
<entry><literal>interval '00:20'</literal></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
</row>
</tbody>
</tgroup>
</table>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<table id="functions-datetime-table">
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<title>Date/Time Functions</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="5">
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<thead>
<row>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<entry>Name</entry>
<entry>Return Type</entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>Description</entry>
<entry>Example</entry>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<entry>Result</entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
</thead>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<tbody>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>age</function>(<type>timestamp</type>)</entry>
<entry><type>interval</type></entry>
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
<entry>Subtract from today</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>age(timestamp '1957-06-13')</literal></entry>
<entry><literal>43 years 8 mons 3 days</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>age</function>(<type>timestamp</type>, <type>timestamp</type>)</entry>
<entry><type>interval</type></entry>
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
<entry>Subtract arguments</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>age('2001-04-10', timestamp '1957-06-13')</literal></entry>
<entry><literal>43 years 9 mons 27 days</literal></entry>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>current_date</function></entry>
<entry><type>date</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Today's date; see <xref linkend="functions-datetime-current">
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</entry>
<entry></entry>
<entry></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<row>
Add LOCALTIME and LOCALTIMESTAMP functions per SQL99 standard. Remove ODBC-compatible empty parentheses from calls to SQL99 functions for which these parentheses do not match the standard. Update the ODBC driver to ensure compatibility with the ODBC standard for these functions (e.g. CURRENT_TIMESTAMP, CURRENT_USER, etc). Include a new appendix in the User's Guide which lists the labeled features for SQL99 (the labeled features replaced the "basic", "intermediate", and "advanced" categories from SQL92). features.sgml does not yet split this list into "supported" and "unsupported" lists.
2002-06-15 05:00:09 +02:00
<entry><function>current_time</function></entry>
<entry><type>time with time zone</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Time of day; see <xref linkend="functions-datetime-current">
Add LOCALTIME and LOCALTIMESTAMP functions per SQL99 standard. Remove ODBC-compatible empty parentheses from calls to SQL99 functions for which these parentheses do not match the standard. Update the ODBC driver to ensure compatibility with the ODBC standard for these functions (e.g. CURRENT_TIMESTAMP, CURRENT_USER, etc). Include a new appendix in the User's Guide which lists the labeled features for SQL99 (the labeled features replaced the "basic", "intermediate", and "advanced" categories from SQL92). features.sgml does not yet split this list into "supported" and "unsupported" lists.
2002-06-15 05:00:09 +02:00
</entry>
<entry></entry>
<entry></entry>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>current_timestamp</function></entry>
Add LOCALTIME and LOCALTIMESTAMP functions per SQL99 standard. Remove ODBC-compatible empty parentheses from calls to SQL99 functions for which these parentheses do not match the standard. Update the ODBC driver to ensure compatibility with the ODBC standard for these functions (e.g. CURRENT_TIMESTAMP, CURRENT_USER, etc). Include a new appendix in the User's Guide which lists the labeled features for SQL99 (the labeled features replaced the "basic", "intermediate", and "advanced" categories from SQL92). features.sgml does not yet split this list into "supported" and "unsupported" lists.
2002-06-15 05:00:09 +02:00
<entry><type>timestamp with time zone</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Date and time; see <xref linkend="functions-datetime-current">
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</entry>
<entry></entry>
<entry></entry>
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>date_part</function>(<type>text</type>, <type>timestamp</type>)</entry>
<entry><type>double precision</type></entry>
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
<entry>Get subfield (equivalent to
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<function>extract</function>); see also <link
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
linkend="functions-datetime-datepart">below</link>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>date_part('hour', timestamp '2001-02-16 20:38:40')</literal></entry>
<entry><literal>20</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>date_part</function>(<type>text</type>, <type>interval</type>)</entry>
<entry><type>double precision</type></entry>
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
<entry>Get subfield (equivalent to
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<function>extract</function>); see also <link
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
linkend="functions-datetime-datepart">below</link>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>date_part('month', interval '2 years 3 months')</literal></entry>
<entry><literal>3</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>date_trunc</function>(<type>text</type>, <type>timestamp</type>)</entry>
<entry><type>timestamp</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Truncate to specified precision; see also <xref
linkend="functions-datetime-trunc">
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>date_trunc('hour', timestamp '2001-02-16 20:38:40')</literal></entry>
<entry><literal>2001-02-16 20:00:00+00</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>extract</function>(<parameter>field</parameter> from
<type>timestamp</type>)</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>double precision</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Get subfield; see also <xref
linkend="functions-datetime-extract">
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>extract(hour from timestamp '2001-02-16 20:38:40')</literal></entry>
<entry><literal>20</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>extract</function>(<parameter>field</parameter> from
<type>interval</type>)</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><type>double precision</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Get subfield; see also <xref
linkend="functions-datetime-extract">
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>extract(month from interval '2 years 3 months')</literal></entry>
<entry><literal>3</literal></entry>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>isfinite</function>(<type>timestamp</type>)</entry>
<entry><type>boolean</type></entry>
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
<entry>Test for finite time stamp (neither invalid nor infinity)</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>isfinite(timestamp '2001-02-16 21:28:30')</literal></entry>
<entry><literal>true</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>isfinite</function>(<type>interval</type>)</entry>
<entry><type>boolean</type></entry>
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
<entry>Test for finite interval</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>isfinite(interval '4 hours')</literal></entry>
<entry><literal>true</literal></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
Add LOCALTIME and LOCALTIMESTAMP functions per SQL99 standard. Remove ODBC-compatible empty parentheses from calls to SQL99 functions for which these parentheses do not match the standard. Update the ODBC driver to ensure compatibility with the ODBC standard for these functions (e.g. CURRENT_TIMESTAMP, CURRENT_USER, etc). Include a new appendix in the User's Guide which lists the labeled features for SQL99 (the labeled features replaced the "basic", "intermediate", and "advanced" categories from SQL92). features.sgml does not yet split this list into "supported" and "unsupported" lists.
2002-06-15 05:00:09 +02:00
<row>
<entry><function>localtime</function></entry>
<entry><type>time</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Time of day; see <xref linkend="functions-datetime-current">
Add LOCALTIME and LOCALTIMESTAMP functions per SQL99 standard. Remove ODBC-compatible empty parentheses from calls to SQL99 functions for which these parentheses do not match the standard. Update the ODBC driver to ensure compatibility with the ODBC standard for these functions (e.g. CURRENT_TIMESTAMP, CURRENT_USER, etc). Include a new appendix in the User's Guide which lists the labeled features for SQL99 (the labeled features replaced the "basic", "intermediate", and "advanced" categories from SQL92). features.sgml does not yet split this list into "supported" and "unsupported" lists.
2002-06-15 05:00:09 +02:00
</entry>
<entry></entry>
<entry></entry>
</row>
<row>
<entry><function>localtimestamp</function></entry>
<entry><type>timestamp</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Date and time; see <xref linkend="functions-datetime-current">
Add LOCALTIME and LOCALTIMESTAMP functions per SQL99 standard. Remove ODBC-compatible empty parentheses from calls to SQL99 functions for which these parentheses do not match the standard. Update the ODBC driver to ensure compatibility with the ODBC standard for these functions (e.g. CURRENT_TIMESTAMP, CURRENT_USER, etc). Include a new appendix in the User's Guide which lists the labeled features for SQL99 (the labeled features replaced the "basic", "intermediate", and "advanced" categories from SQL92). features.sgml does not yet split this list into "supported" and "unsupported" lists.
2002-06-15 05:00:09 +02:00
</entry>
<entry></entry>
<entry></entry>
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>now</function>()</entry>
Fix breakage in new-in-7.3 timetz_zone() function: was giving random results due to doing arithmetic on uninitialized values. Add some documentation about the AT TIME ZONE construct. Update some other date/time documentation that seemed out of date for 7.3.
2002-11-22 00:31:20 +01:00
<entry><type>timestamp with time zone</type></entry>
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
<entry>Current date and time (equivalent to
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<function>current_timestamp</function>); see <xref
linkend="functions-datetime-current">
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</entry>
<entry></entry>
<entry></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>timeofday()</function></entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Current date and time; see <xref
linkend="functions-datetime-current">
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>timeofday()</literal></entry>
<entry><literal>Wed Feb 21 17:01:13.000126 2001 EST</literal></entry>
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
</row>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</tbody>
</tgroup>
</table>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<sect2 id="functions-datetime-extract">
<title><function>EXTRACT</function>, <function>date_part</function></title>
<synopsis>
EXTRACT (<replaceable>field</replaceable> FROM <replaceable>source</replaceable>)
</synopsis>
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The <function>extract</function> function retrieves subfields
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
from date/time values, such as year or hour.
<replaceable>source</replaceable> is a value expression that
evaluates to type <type>timestamp</type> or <type>interval</type>.
(Expressions of type <type>date</type> or <type>time</type> will
be cast to <type>timestamp</type> and can therefore be used as
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
well.) <replaceable>field</replaceable> is an identifier or
string that selects what field to extract from the source value.
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
The <function>extract</function> function returns values of type
<type>double precision</type>.
The following are valid values:
<!-- alphabetical -->
<variablelist>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>century</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The year field divided by 100
</para>
<screen>
SELECT EXTRACT(CENTURY FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>20</computeroutput>
</screen>
<para>
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
Note that the result for the century field is simply the year field
divided by 100, and not the conventional definition which puts most
years in the 1900's in the twentieth century.
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</para>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>day</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The day (of the month) field (1 - 31)
</para>
<screen>
SELECT EXTRACT(DAY FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>16</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>decade</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The year field divided by 10
</para>
<screen>
SELECT EXTRACT(DECADE FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>200</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>dow</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The day of the week (0 - 6; Sunday is 0) (for
<type>timestamp</type> values only)
</para>
<screen>
SELECT EXTRACT(DOW FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>5</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>doy</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The day of the year (1 - 365/366) (for <type>timestamp</type> values only)
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<screen>
SELECT EXTRACT(DOY FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>47</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>epoch</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
For <type>date</type> and <type>timestamp</type> values, the
Fix breakage in new-in-7.3 timetz_zone() function: was giving random results due to doing arithmetic on uninitialized values. Add some documentation about the AT TIME ZONE construct. Update some other date/time documentation that seemed out of date for 7.3.
2002-11-22 00:31:20 +01:00
number of seconds since 1970-01-01 00:00:00-00 (can be negative);
for <type>interval</type> values, the total number
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
of seconds in the interval
</para>
<screen>
SELECT EXTRACT(EPOCH FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>982352320</computeroutput>
SELECT EXTRACT(EPOCH FROM INTERVAL '5 days 3 hours');
<lineannotation>Result: </lineannotation><computeroutput>442800</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>hour</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The hour field (0 - 23)
</para>
<screen>
SELECT EXTRACT(HOUR FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>20</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>microseconds</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The seconds field, including fractional parts, multiplied by 1
000 000. Note that this includes full seconds.
</para>
<screen>
SELECT EXTRACT(MICROSECONDS FROM TIME '17:12:28.5');
<lineannotation>Result: </lineannotation><computeroutput>28500000</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>millennium</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The year field divided by 1000
</para>
<screen>
SELECT EXTRACT(MILLENNIUM FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>2</computeroutput>
</screen>
<para>
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
Note that the result for the millennium field is simply the year field
divided by 1000, and not the conventional definition which puts
years in the 1900's in the second millennium.
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</para>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>milliseconds</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The seconds field, including fractional parts, multiplied by
1000. Note that this includes full seconds.
</para>
<screen>
SELECT EXTRACT(MILLISECONDS FROM TIME '17:12:28.5');
<lineannotation>Result: </lineannotation><computeroutput>28500</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>minute</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The minutes field (0 - 59)
</para>
<screen>
SELECT EXTRACT(MINUTE FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>38</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>month</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
For <type>timestamp</type> values, the number of the month
within the year (1 - 12) ; for <type>interval</type> values
the number of months, modulo 12 (0 - 11)
</para>
<screen>
SELECT EXTRACT(MONTH FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>2</computeroutput>
SELECT EXTRACT(MONTH FROM INTERVAL '2 years 3 months');
<lineannotation>Result: </lineannotation><computeroutput>3</computeroutput>
SELECT EXTRACT(MONTH FROM INTERVAL '2 years 13 months');
<lineannotation>Result: </lineannotation><computeroutput>1</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>quarter</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The quarter of the year (1 - 4) that the day is in (for
<type>timestamp</type> values only)
</para>
<screen>
SELECT EXTRACT(QUARTER FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>1</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>second</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The seconds field, including fractional parts (0 -
59<footnote><simpara>60 if leap seconds are
implemented by the operating system</simpara></footnote>)
</para>
<screen>
SELECT EXTRACT(SECOND FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>40</computeroutput>
SELECT EXTRACT(SECOND FROM TIME '17:12:28.5');
<lineannotation>Result: </lineannotation><computeroutput>28.5</computeroutput>
</screen>
</listitem>
</varlistentry>
Remove gratuitous discrepancy between extract() and date_part(), regarding timezone_hour, timezone_minute vs. tz_hour, tz_minute. Document the former.
2001-10-10 02:02:42 +02:00
<!--
<varlistentry>
<term><literal>timezone</literal></term>
<listitem>
<para>
The time zone offset. XXX But in what units?
</para>
</listitem>
</varlistentry>
-->
<varlistentry>
<term><literal>timezone_hour</literal></term>
<listitem>
<para>
The hour component of the time zone offset.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>timezone_minute</literal></term>
<listitem>
<para>
The minute component of the time zone offset.
</para>
</listitem>
</varlistentry>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>week</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
From a <type>timestamp</type> value, calculate the number of
the week of the year that the day is in. By definition
(<acronym>ISO</acronym> 8601), the first week of a year
contains January 4 of that year. (The <acronym>ISO</acronym>
week starts on Monday.) In other words, the first Thursday of
a year is in week 1 of that year.
</para>
<screen>
SELECT EXTRACT(WEEK FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>7</computeroutput>
</screen>
</listitem>
</varlistentry>
<varlistentry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<term><literal>year</literal></term>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<listitem>
<para>
The year field
</para>
<screen>
SELECT EXTRACT(YEAR FROM TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>2001</computeroutput>
</screen>
</listitem>
</varlistentry>
</variablelist>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</para>
<para>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
The <function>extract</function> function is primarily intended
for computational processing. For formatting date/time values for
display, see <xref linkend="functions-formatting">.
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</para>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<anchor id="functions-datetime-datepart">
<para>
Final markup for 7.1 hardcopy release. Mostly typo and table-fitting adjustments. Note that many tables are being abused with *really* long description columns. Should probably shrink those columns to be more concise, and move some of the info to follow-on reference notes.
2001-04-20 17:52:33 +02:00
The <function>date_part</function> function is modeled on the traditional
<productname>Ingres</productname> equivalent to the
Fix breakage in new-in-7.3 timetz_zone() function: was giving random results due to doing arithmetic on uninitialized values. Add some documentation about the AT TIME ZONE construct. Update some other date/time documentation that seemed out of date for 7.3.
2002-11-22 00:31:20 +01:00
<acronym>SQL</acronym>-standard function <function>extract</function>:
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<synopsis>
date_part('<replaceable>field</replaceable>', <replaceable>source</replaceable>)
</synopsis>
Fix breakage in new-in-7.3 timetz_zone() function: was giving random results due to doing arithmetic on uninitialized values. Add some documentation about the AT TIME ZONE construct. Update some other date/time documentation that seemed out of date for 7.3.
2002-11-22 00:31:20 +01:00
Note that here the <replaceable>field</replaceable> parameter needs to
be a string value, not a name. The valid field values for
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<function>date_part</function> are the same as for
<function>extract</function>.
</para>
<screen>
SELECT date_part('day', TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>16</computeroutput>
Add missing ';'
2001-09-10 04:46:18 +02:00
SELECT date_part('hour', INTERVAL '4 hours 3 minutes');
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<lineannotation>Result: </lineannotation><computeroutput>4</computeroutput>
</screen>
</sect2>
<sect2 id="functions-datetime-trunc">
<title><function>date_trunc</function></title>
<para>
The function <function>date_trunc</function> is conceptually
similar to the <function>trunc</function> function for numbers.
</para>
<para>
<synopsis>
date_trunc('<replaceable>field</replaceable>', <replaceable>source</replaceable>)
</synopsis>
<replaceable>source</replaceable> is a value expression of type
<type>timestamp</type> (values of type <type>date</type> and
<type>time</type> are cast automatically).
<replaceable>field</replaceable> selects to which precision to
truncate the time stamp value. The return value is of type
<type>timestamp</type> with all fields that are less than the
selected one set to zero (or one, for day and month).
</para>
<para>
Valid values for <replaceable>field</replaceable> are:
<simplelist>
<member>microseconds</member>
<member>milliseconds</member>
<member>second</member>
<member>minute</member>
<member>hour</member>
<member>day</member>
<member>month</member>
<member>year</member>
<member>decade</member>
<member>century</member>
<member>millennium</member>
</simplelist>
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
Examples:
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<screen>
SELECT date_trunc('hour', TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>2001-02-16 20:00:00+00</computeroutput>
SELECT date_trunc('year', TIMESTAMP '2001-02-16 20:38:40');
<lineannotation>Result: </lineannotation><computeroutput>2001-01-01 00:00:00+00</computeroutput>
</screen>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</para>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</sect2>
Fix breakage in new-in-7.3 timetz_zone() function: was giving random results due to doing arithmetic on uninitialized values. Add some documentation about the AT TIME ZONE construct. Update some other date/time documentation that seemed out of date for 7.3.
2002-11-22 00:31:20 +01:00
<sect2 id="functions-datetime-zoneconvert">
<title><function>AT TIME ZONE</function></title>
<indexterm>
<primary>timezone</primary>
<secondary>conversion</secondary>
</indexterm>
<para>
The <function>AT TIME ZONE</function> construct allows conversions
of timestamps to different timezones.
</para>
<table id="functions-datetime-zoneconvert-table">
<title>AT TIME ZONE Variants</title>
<tgroup cols="3">
<thead>
<row>
<entry>Expression</entry>
<entry>Returns</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>
<type>timestamp without time zone</type>
<literal>AT TIME ZONE</literal>
<replaceable>zone</>
</entry>
<entry><type>timestamp with time zone</type></entry>
<entry>Convert local time in given timezone to UTC</entry>
</row>
<row>
<entry>
<type>timestamp with time zone</type>
<literal>AT TIME ZONE</literal>
<replaceable>zone</>
</entry>
<entry><type>timestamp without time zone</type></entry>
<entry>Convert UTC to local time in given timezone</entry>
</row>
<row>
<entry>
<type>time with time zone</type>
<literal>AT TIME ZONE</literal>
<replaceable>zone</>
</entry>
<entry><type>time with time zone</type></entry>
<entry>Convert local time across timezones</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
In these expressions, the desired time <replaceable>zone</> can be
specified either as a text string (e.g., <literal>'PST'</literal>)
or as an interval (e.g., <literal>INTERVAL '-08:00'</literal>).
</para>
<para>
Examples (supposing that <varname>TimeZone</> is <literal>PST8PDT</>):
<screen>
SELECT TIMESTAMP '2001-02-16 20:38:40' AT TIME ZONE 'MST';
<lineannotation>Result: </lineannotation><computeroutput>2001-02-16 19:38:40-08</computeroutput>
SELECT TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40-05' AT TIME ZONE 'MST';
<lineannotation>Result: </lineannotation><computeroutput>2001-02-16 18:38:40</computeroutput>
</screen>
The first example takes a zone-less timestamp and interprets it as MST time
(GMT-7) to produce a UTC timestamp, which is then rotated to PST (GMT-8)
for display. The second example takes a timestamp specified in EST
(GMT-5) and converts it to local time in MST (GMT-7).
</para>
<para>
The function <function>timezone</function>(<replaceable>zone</>,
<replaceable>timestamp</>) is equivalent to the SQL-compliant construct
<replaceable>timestamp</> <literal>AT TIME ZONE</literal>
<replaceable>zone</>.
</para>
</sect2>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<sect2 id="functions-datetime-current">
<title>Current Date/Time</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>current</secondary>
</indexterm>
<indexterm>
<primary>time</primary>
<secondary>current</secondary>
</indexterm>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<para>
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
The following functions are available to obtain the current date and/or
time:
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<synopsis>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
CURRENT_DATE
Update description of CURRENT_TIMESTAMP and friends.
2001-12-23 21:22:49 +01:00
CURRENT_TIME
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
CURRENT_TIMESTAMP
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
CURRENT_TIME ( <replaceable>precision</replaceable> )
CURRENT_TIMESTAMP ( <replaceable>precision</replaceable> )
Add LOCALTIME and LOCALTIMESTAMP functions per SQL99 standard. Remove ODBC-compatible empty parentheses from calls to SQL99 functions for which these parentheses do not match the standard. Update the ODBC driver to ensure compatibility with the ODBC standard for these functions (e.g. CURRENT_TIMESTAMP, CURRENT_USER, etc). Include a new appendix in the User's Guide which lists the labeled features for SQL99 (the labeled features replaced the "basic", "intermediate", and "advanced" categories from SQL92). features.sgml does not yet split this list into "supported" and "unsupported" lists.
2002-06-15 05:00:09 +02:00
LOCALTIME
LOCALTIMESTAMP
LOCALTIME ( <replaceable>precision</replaceable> )
LOCALTIMESTAMP ( <replaceable>precision</replaceable> )
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</synopsis>
Fix breakage in new-in-7.3 timetz_zone() function: was giving random results due to doing arithmetic on uninitialized values. Add some documentation about the AT TIME ZONE construct. Update some other date/time documentation that seemed out of date for 7.3.
2002-11-22 00:31:20 +01:00
</para>
<para>
<function>CURRENT_TIME</function> and
<function>CURRENT_TIMESTAMP</function> deliver values with time zone;
<function>LOCALTIME</function> and
<function>LOCALTIMESTAMP</function> deliver values without time zone.
</para>
<para>
Add LOCALTIME and LOCALTIMESTAMP functions per SQL99 standard. Remove ODBC-compatible empty parentheses from calls to SQL99 functions for which these parentheses do not match the standard. Update the ODBC driver to ensure compatibility with the ODBC standard for these functions (e.g. CURRENT_TIMESTAMP, CURRENT_USER, etc). Include a new appendix in the User's Guide which lists the labeled features for SQL99 (the labeled features replaced the "basic", "intermediate", and "advanced" categories from SQL92). features.sgml does not yet split this list into "supported" and "unsupported" lists.
2002-06-15 05:00:09 +02:00
<function>CURRENT_TIME</function>,
<function>CURRENT_TIMESTAMP</function>,
<function>LOCALTIME</function>, and
<function>LOCALTIMESTAMP</function>
can optionally be given
a precision parameter, which causes the result to be rounded
to that many fractional digits. Without a precision parameter,
the result is given to the full available precision.
Update description of CURRENT_TIMESTAMP and friends.
2001-12-23 21:22:49 +01:00
</para>
Add LOCALTIME and LOCALTIMESTAMP functions per SQL99 standard. Remove ODBC-compatible empty parentheses from calls to SQL99 functions for which these parentheses do not match the standard. Update the ODBC driver to ensure compatibility with the ODBC standard for these functions (e.g. CURRENT_TIMESTAMP, CURRENT_USER, etc). Include a new appendix in the User's Guide which lists the labeled features for SQL99 (the labeled features replaced the "basic", "intermediate", and "advanced" categories from SQL92). features.sgml does not yet split this list into "supported" and "unsupported" lists.
2002-06-15 05:00:09 +02:00
<note>
<para>
Prior to <productname>PostgreSQL</productname> 7.2, the precision
parameters were unimplemented, and the result was always given
in integer seconds.
</para>
</note>
Update description of CURRENT_TIMESTAMP and friends.
2001-12-23 21:22:49 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
Some examples:
<screen>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
SELECT CURRENT_TIME;
Update description of CURRENT_TIMESTAMP and friends.
2001-12-23 21:22:49 +01:00
<computeroutput>14:39:53.662522-05</computeroutput>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
SELECT CURRENT_DATE;
Update description of CURRENT_TIMESTAMP and friends.
2001-12-23 21:22:49 +01:00
<computeroutput>2001-12-23</computeroutput>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
SELECT CURRENT_TIMESTAMP;
Update description of CURRENT_TIMESTAMP and friends.
2001-12-23 21:22:49 +01:00
<computeroutput>2001-12-23 14:39:53.662522-05</computeroutput>
SELECT CURRENT_TIMESTAMP(2);
<computeroutput>2001-12-23 14:39:53.66-05</computeroutput>
Add LOCALTIME and LOCALTIMESTAMP functions per SQL99 standard. Remove ODBC-compatible empty parentheses from calls to SQL99 functions for which these parentheses do not match the standard. Update the ODBC driver to ensure compatibility with the ODBC standard for these functions (e.g. CURRENT_TIMESTAMP, CURRENT_USER, etc). Include a new appendix in the User's Guide which lists the labeled features for SQL99 (the labeled features replaced the "basic", "intermediate", and "advanced" categories from SQL92). features.sgml does not yet split this list into "supported" and "unsupported" lists.
2002-06-15 05:00:09 +02:00
SELECT LOCALTIMESTAMP;
<computeroutput>2001-12-23 14:39:53.662522</computeroutput>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</screen>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</para>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<para>
The function <function>now()</function> is the 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
<productname>PostgreSQL</productname> equivalent to
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<function>CURRENT_TIMESTAMP</function>.
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
</para>
<para>
Update description of CURRENT_TIMESTAMP and friends.
2001-12-23 21:22:49 +01:00
There is also <function>timeofday()</function>, which for historical
reasons returns a text string rather than a <type>timestamp</type> value:
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
<screen>
SELECT timeofday();
Sat Feb 17 19:07:32.000126 2001 EST
</screen>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</para>
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
<para>
Add more documentation about CURRENT_TIMESTAMP. Also, code < and > as &lt;/&gt; for cleaner SGML.
2002-10-05 21:03:16 +02:00
It is important to realize that
<function>CURRENT_TIMESTAMP</function> and related functions return
the start time of the current transaction; their values do not
change during the transaction. <function>timeofday()</function>
returns the wall clock time and does advance during transactions.
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
</para>
Fix markup error.
2002-10-06 01:43:42 +02:00
<note>
<para>
Many other database systems advance these values more
frequently.
</para>
Add more documentation about CURRENT_TIMESTAMP. Also, code < and > as &lt;/&gt; for cleaner SGML.
2002-10-05 21:03:16 +02:00
</note>
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
<para>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
All the date/time data types also accept the special literal value
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<literal>now</literal> to specify the current date and time. Thus,
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
the following three all return the same result:
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<programlisting>
SELECT CURRENT_TIMESTAMP;
SELECT now();
SELECT TIMESTAMP 'now';
</programlisting>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</para>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
<note>
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
You do not want to use the third form when specifying a <literal>DEFAULT</>
clause while creating a table. The system will convert <literal>now</literal>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
to a <type>timestamp</type> as soon as the constant is parsed, so that when
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
the default value is needed,
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
the time of the table creation would be used! The first two
forms will not be evaluated until the default value is used,
Document timeofday(), mention start-of-transaction vs. current-time semantics, a few other small improvements.
2001-02-22 00:15:24 +01:00
because they are function calls. Thus they will give the desired
behavior of defaulting to the time of row insertion.
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
</para>
</note>
</sect2>
</sect1>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<sect1 id="functions-geometry">
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<title>Geometric Functions and Operators</title>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<para>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
The geometric types <type>point</type>, <type>box</type>,
<type>lseg</type>, <type>line</type>, <type>path</type>,
<type>polygon</type>, and <type>circle</type> have a large set of
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
native support functions and operators, shown in <xref
linkend="functions-geometry-op-table">, <xref
linkend="functions-geometry-func-table">, and <xref
linkend="functions-geometry-conv-table">.
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table id="functions-geometry-op-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title>Geometric Operators</title>
<tgroup cols="3">
<thead>
<row>
<entry>Operator</entry>
<entry>Description</entry>
<entry>Usage</entry>
</row>
</thead>
<tbody>
<row>
<entry> + </entry>
<entry>Translation</entry>
<entry><literal>box '((0,0),(1,1))' + point '(2.0,0)'</literal></entry>
</row>
<row>
<entry> - </entry>
<entry>Translation</entry>
<entry><literal>box '((0,0),(1,1))' - point '(2.0,0)'</literal></entry>
</row>
<row>
<entry> * </entry>
<entry>Scaling/rotation</entry>
<entry><literal>box '((0,0),(1,1))' * point '(2.0,0)'</literal></entry>
</row>
<row>
<entry> / </entry>
<entry>Scaling/rotation</entry>
<entry><literal>box '((0,0),(2,2))' / point '(2.0,0)'</literal></entry>
</row>
<row>
<entry> # </entry>
<entry>Intersection</entry>
<entry><literal>'((1,-1),(-1,1))' # '((1,1),(-1,-1))'</literal></entry>
</row>
<row>
<entry> # </entry>
Some improvements in geometric-operators documentation.
2002-08-08 16:29:07 +02:00
<entry>Number of points in path or polygon</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><literal># '((1,0),(0,1),(-1,0))'</literal></entry>
</row>
<row>
<entry> ## </entry>
<entry>Point of closest proximity</entry>
<entry><literal>point '(0,0)' ## lseg '((2,0),(0,2))'</literal></entry>
</row>
<row>
<entry> &amp;&amp; </entry>
<entry>Overlaps?</entry>
<entry><literal>box '((0,0),(1,1))' &amp;&amp; box '((0,0),(2,2))'</literal></entry>
</row>
<row>
<entry> &amp;&lt; </entry>
<entry>Overlaps to left?</entry>
<entry><literal>box '((0,0),(1,1))' &amp;&lt; box '((0,0),(2,2))'</literal></entry>
</row>
<row>
<entry> &amp;&gt; </entry>
<entry>Overlaps to right?</entry>
<entry><literal>box '((0,0),(3,3))' &amp;&gt; box '((0,0),(2,2))'</literal></entry>
</row>
<row>
<entry> &lt;-&gt; </entry>
<entry>Distance between</entry>
<entry><literal>circle '((0,0),1)' &lt;-&gt; circle '((5,0),1)'</literal></entry>
</row>
<row>
<entry> &lt;&lt; </entry>
<entry>Left of?</entry>
<entry><literal>circle '((0,0),1)' &lt;&lt; circle '((5,0),1)'</literal></entry>
</row>
<row>
<entry> &lt;^ </entry>
<entry>Is below?</entry>
<entry><literal>circle '((0,0),1)' &lt;^ circle '((0,5),1)'</literal></entry>
</row>
<row>
<entry> &gt;&gt; </entry>
<entry>Is right of?</entry>
<entry><literal>circle '((5,0),1)' &gt;&gt; circle '((0,0),1)'</literal></entry>
</row>
<row>
<entry> &gt;^ </entry>
<entry>Is above?</entry>
<entry><literal>circle '((0,5),1)' >^ circle '((0,0),1)'</literal></entry>
</row>
<row>
<entry> ?# </entry>
<entry>Intersects or overlaps</entry>
<entry><literal>lseg '((-1,0),(1,0))' ?# box '((-2,-2),(2,2))'</literal></entry>
</row>
<row>
<entry> ?- </entry>
<entry>Is horizontal?</entry>
<entry><literal>point '(1,0)' ?- point '(0,0)'</literal></entry>
</row>
<row>
<entry> ?-| </entry>
<entry>Is perpendicular?</entry>
<entry><literal>lseg '((0,0),(0,1))' ?-| lseg '((0,0),(1,0))'</literal></entry>
</row>
<row>
<entry> @-@ </entry>
<entry>Length or circumference</entry>
<entry><literal>@-@ path '((0,0),(1,0))'</literal></entry>
</row>
<row>
<entry> ?| </entry>
<entry>Is vertical?</entry>
<entry><literal>point '(0,1)' ?| point '(0,0)'</literal></entry>
</row>
<row>
<entry> ?|| </entry>
<entry>Is parallel?</entry>
<entry><literal>lseg '((-1,0),(1,0))' ?|| lseg '((-1,2),(1,2))'</literal></entry>
</row>
<row>
<entry> @ </entry>
<entry>Contained or on</entry>
<entry><literal>point '(1,1)' @ circle '((0,0),2)'</literal></entry>
</row>
<row>
<entry> @@ </entry>
<entry>Center of</entry>
<entry><literal>@@ circle '((0,0),10)'</literal></entry>
</row>
<row>
<entry> ~= </entry>
<entry>Same as</entry>
<entry><literal>polygon '((0,0),(1,1))' ~= polygon '((1,1),(0,0))'</literal></entry>
</row>
</tbody>
</tgroup>
</table>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table id="functions-geometry-func-table">
Minor updates for release.
1999-06-14 09:36:12 +02:00
<title>Geometric Functions</title>
<tgroup cols="4">
<thead>
<row>
<entry>Function</entry>
<entry>Returns</entry>
<entry>Description</entry>
<entry>Example</entry>
</row>
</thead>
<tbody>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>area</function>(object)</entry>
<entry><type>double precision</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>area of item</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>area(box '((0,0),(1,1))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>box</function>(box, box)</entry>
<entry><type>box</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>intersection box</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>box(box '((0,0),(1,1))',box '((0.5,0.5),(2,2))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>center</function>(object)</entry>
<entry><type>point</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>center of item</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>center(box '((0,0),(1,2))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>diameter</function>(circle)</entry>
<entry><type>double precision</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>diameter of circle</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>diameter(circle '((0,0),2.0)')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>height</function>(box)</entry>
<entry><type>double precision</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>vertical size of box</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>height(box '((0,0),(1,1))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>isclosed</function>(path)</entry>
<entry><type>boolean</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>a closed path?</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>isclosed(path '((0,0),(1,1),(2,0))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>isopen</function>(path)</entry>
<entry><type>boolean</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>an open path?</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>isopen(path '[(0,0),(1,1),(2,0)]')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>length</function>(object)</entry>
<entry><type>double precision</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>length of item</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>length(path '((-1,0),(1,0))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
Some improvements in geometric-operators documentation.
2002-08-08 16:29:07 +02:00
<row>
<entry><function>npoints</function>(path)</entry>
<entry><type>integer</type></entry>
<entry>number of points</entry>
<entry><literal>npoints(path '[(0,0),(1,1),(2,0)]')</literal></entry>
</row>
<row>
<entry><function>npoints</function>(polygon)</entry>
<entry><type>integer</type></entry>
<entry>number of points</entry>
<entry><literal>npoints(polygon '((1,1),(0,0))')</literal></entry>
</row>
Minor updates for release.
1999-06-14 09:36:12 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>pclose</function>(path)</entry>
<entry><type>path</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>convert path to closed</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>popen(path '[(0,0),(1,1),(2,0)]')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<![IGNORE[
<!-- Not defined by this name. Implements the intersection operator '#' -->
Minor updates for release.
1999-06-14 09:36:12 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>point</function>(lseg,lseg)</entry>
<entry><type>point</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>intersection</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>point(lseg '((-1,0),(1,0))',lseg '((-2,-2),(2,2))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
]]>
Minor updates for release.
1999-06-14 09:36:12 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>popen</function>(path)</entry>
<entry><type>path</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>convert path to open path</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>popen(path '((0,0),(1,1),(2,0))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>radius</function>(circle)</entry>
<entry><type>double precision</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>radius of circle</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>radius(circle '((0,0),2.0)')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>width</function>(box)</entry>
<entry><type>double precision</type></entry>
Start updating for the v7.0 release. Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 19:14:43 +02:00
<entry>horizontal size</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>width(box '((0,0),(1,1))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
</tbody>
</tgroup>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</table>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table id="functions-geometry-conv-table">
Minor updates for release.
1999-06-14 09:36:12 +02:00
<title>Geometric Type Conversion Functions</title>
<tgroup cols="4">
<thead>
<row>
<entry>Function</entry>
<entry>Returns</entry>
<entry>Description</entry>
<entry>Example</entry>
</row>
</thead>
<tbody>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>box</function>(<type>circle</type>)</entry>
<entry><type>box</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>circle to box</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>box(circle '((0,0),2.0)')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>box</function>(<type>point</type>, <type>point</type>)</entry>
<entry><type>box</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>points to box</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>box(point '(0,0)', point '(1,1)')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>box</function>(<type>polygon</type>)</entry>
<entry><type>box</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>polygon to box</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>box(polygon '((0,0),(1,1),(2,0))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>circle</function>(<type>box</type>)</entry>
<entry><type>circle</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>to circle</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>circle(box '((0,0),(1,1))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>circle</function>(<type>point</type>, <type>double precision</type>)</entry>
<entry><type>circle</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>point to circle</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>circle(point '(0,0)', 2.0)</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>lseg</function>(<type>box</type>)</entry>
<entry><type>lseg</type></entry>
Spell checking and markup additions
2002-03-22 20:20:45 +01:00
<entry>box diagonal to <type>lseg</type></entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>lseg(box '((-1,0),(1,0))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>lseg</function>(<type>point</type>, <type>point</type>)</entry>
<entry><type>lseg</type></entry>
Spell checking and markup additions
2002-03-22 20:20:45 +01:00
<entry>points to <type>lseg</type></entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>lseg(point '(-1,0)', point '(1,0)')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>path</function>(<type>polygon</type>)</entry>
<entry><type>point</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>polygon to path</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>path(polygon '((0,0),(1,1),(2,0))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>point</function>(<type>circle</type>)</entry>
<entry><type>point</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>center</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>point(circle '((0,0),2.0)')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>point</function>(<type>lseg</type>, <type>lseg</type>)</entry>
<entry><type>point</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>intersection</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>point(lseg '((-1,0),(1,0))', lseg '((-2,-2),(2,2))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>point</function>(<type>polygon</type>)</entry>
<entry><type>point</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>center</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>point(polygon '((0,0),(1,1),(2,0))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>polygon</function>(<type>box</type>)</entry>
<entry><type>polygon</type></entry>
Some improvements in geometric-operators documentation.
2002-08-08 16:29:07 +02:00
<entry>4-point polygon</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>polygon(box '((0,0),(1,1))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>polygon</function>(<type>circle</type>)</entry>
<entry><type>polygon</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>12-point polygon</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>polygon(circle '((0,0),2.0)')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>polygon</function>(<replaceable class="parameter">npts</replaceable>, <type>circle</type>)</entry>
<entry><type>polygon</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry><replaceable class="parameter">npts</replaceable> polygon</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>polygon(12, circle '((0,0),2.0)')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>polygon</function>(<type>path</type>)</entry>
<entry><type>polygon</type></entry>
Fixups in content and markup for 7.0 release.
2000-05-02 22:02:03 +02:00
<entry>path to polygon</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>polygon(path '((0,0),(1,1),(2,0))')</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
</tbody>
</tgroup>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</table>
Some improvements in geometric-operators documentation.
2002-08-08 16:29:07 +02:00
<para>
It is possible to access the two component numbers of a <type>point</>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
as though it were an array with subscripts 0, 1. For example, if
Some improvements in geometric-operators documentation.
2002-08-08 16:29:07 +02:00
<literal>t.p</> is a <type>point</> column then
<literal>SELECT p[0] FROM t</> retrieves the X coordinate;
<literal>UPDATE t SET p[1] = ...</> changes the Y coordinate.
In the same way, a <type>box</> or an <type>lseg</> may be treated
as an array of two <type>point</>s.
</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
</sect1>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect1 id="functions-net">
<title>Network Address Type Functions</title>
Include new cidr and inet data types.
1998-10-27 07:14:41 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="cidr-inet-operators-table"> shows the operators
available for the <type>inet</type> and <type>cidr</type> types.
The operators <literal>&lt;&lt;</literal>,
<literal>&lt;&lt;=</literal>, <literal>&gt;&gt;</literal>,
<literal>&gt;&gt;=</literal> test for subnet inclusion: they
consider only the network parts of the two addresses, ignoring any
host part, and determine whether one network part is identical to
or a subnet of the other.
</para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<table tocentry="1" id="cidr-inet-operators-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title><type>cidr</type> and <type>inet</type> Operators</title>
<tgroup cols="3">
<thead>
<row>
<entry>Operator</entry>
<entry>Description</entry>
<entry>Usage</entry>
</row>
</thead>
<tbody>
<row>
<entry> &lt; </entry>
<entry>Less than</entry>
<entry><literal>inet '192.168.1.5' &lt; inet '192.168.1.6'</literal></entry>
</row>
<row>
<entry> &lt;= </entry>
<entry>Less than or equal</entry>
<entry><literal>inet '192.168.1.5' &lt;= inet '192.168.1.5'</literal></entry>
</row>
<row>
<entry> = </entry>
<entry>Equals</entry>
<entry><literal>inet '192.168.1.5' = inet '192.168.1.5'</literal></entry>
</row>
<row>
<entry> &gt;= </entry>
<entry>Greater or equal</entry>
<entry><literal>inet '192.168.1.5' &gt;= inet '192.168.1.5'</literal></entry>
</row>
<row>
<entry> &gt; </entry>
<entry>Greater</entry>
<entry><literal>inet '192.168.1.5' &gt; inet '192.168.1.4'</literal></entry>
</row>
<row>
<entry> &lt;&gt; </entry>
<entry>Not equal</entry>
<entry><literal>inet '192.168.1.5' &lt;&gt; inet '192.168.1.4'</literal></entry>
</row>
<row>
<entry> &lt;&lt; </entry>
<entry>is contained within</entry>
<entry><literal>inet '192.168.1.5' &lt;&lt; inet '192.168.1/24'</literal></entry>
</row>
<row>
<entry> &lt;&lt;= </entry>
<entry>is contained within or equals</entry>
<entry><literal>inet '192.168.1/24' &lt;&lt;= inet '192.168.1/24'</literal></entry>
</row>
<row>
<entry> &gt;&gt; </entry>
<entry>contains</entry>
<entry><literal>inet'192.168.1/24' &gt;&gt; inet '192.168.1.5'</literal></entry>
</row>
<row>
<entry> &gt;&gt;= </entry>
<entry>contains or equals</entry>
<entry><literal>inet '192.168.1/24' &gt;&gt;= inet '192.168.1/24'</literal></entry>
</row>
</tbody>
</tgroup>
</table>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="cidr-inet-functions-table"> shows the functions
available for use with the <type>inet</type> and <type>cidr</type>
types. The <function>host()</function>,
<function>text()</function>, and <function>abbrev()</function>
functions are primarily intended to offer alternative display
formats. You can cast a text field to inet using normal casting
syntax: <literal>inet(expression)</literal> or
<literal>colname::inet</literal>.
</para>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table tocentry="1" id="cidr-inet-functions-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title><type>cidr</type> and <type>inet</type> Functions</title>
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
<tgroup cols="5">
Minor updates for release.
1999-06-14 09:36:12 +02:00
<thead>
<row>
<entry>Function</entry>
<entry>Returns</entry>
<entry>Description</entry>
<entry>Example</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>Result</entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
</thead>
<tbody>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>broadcast</function>(<type>inet</type>)</entry>
<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>broadcast address for network</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>broadcast('192.168.1.5/24')</literal></entry>
<entry><literal>192.168.1.255/24</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>host</function>(<type>inet</type>)</entry>
<entry><type>text</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>extract IP address as text</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>host('192.168.1.5/24')</literal></entry>
<entry><literal>192.168.1.5</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>masklen</function>(<type>inet</type>)</entry>
<entry><type>integer</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>extract netmask length</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>masklen('192.168.1.5/24')</literal></entry>
<entry><literal>24</literal></entry>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</row>
Docs for: > >> inet(text), cidr(text): convert a text value into inet/cidr > >> set_masklen(inet): set masklen on the inet value Alex Pilosov
2001-06-14 00:51:02 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>set_masklen</function>(<type>inet</type>,<type>integer</type>)</entry>
<entry><type>inet</type></entry>
Spell checking and markup additions
2002-03-22 20:20:45 +01:00
<entry>set netmask length for <type>inet</type> value</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>set_masklen('192.168.1.5/24',16)</literal></entry>
<entry><literal>192.168.1.5/16</literal></entry>
Docs for: > >> inet(text), cidr(text): convert a text value into inet/cidr > >> set_masklen(inet): set masklen on the inet value Alex Pilosov
2001-06-14 00:51:02 +02:00
</row>
Minor updates for release.
1999-06-14 09:36:12 +02:00
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>netmask</function>(<type>inet</type>)</entry>
<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>construct netmask for network</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>netmask('192.168.1.5/24')</literal></entry>
<entry><literal>255.255.255.0</literal></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
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>network</function>(<type>inet</type>)</entry>
<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>extract network part of address</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>network('192.168.1.5/24')</literal></entry>
<entry><literal>192.168.1.0/24</literal></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
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>text</function>(<type>inet</type>)</entry>
<entry><type>text</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>extract IP address and masklen as text</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>text(inet '192.168.1.5')</literal></entry>
<entry><literal>192.168.1.5/32</literal></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
</row>
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
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>abbrev</function>(<type>inet</type>)</entry>
<entry><type>text</type></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>extract abbreviated display as text</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>abbrev(cidr '10.1.0.0/16')</literal></entry>
<entry><literal>10.1/16</literal></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
</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
</tbody>
</tgroup>
</table>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="macaddr-functions-table"> shows the functions
available for use with the <type>mac</type> type. The function
<function>trunc</function>(<type>macaddr</type>) returns a MAC
address with the last 3 bytes set to 0. This can be used to
associate the remaining prefix with a manufacturer. The directory
<filename>contrib/mac</filename> in the source distribution
contains some utilities to create and maintain such an association
table.
</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
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table tocentry="1" id="macaddr-functions-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title><type>macaddr</type> Functions</title>
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
<tgroup cols="5">
<thead>
<row>
<entry>Function</entry>
<entry>Returns</entry>
<entry>Description</entry>
<entry>Example</entry>
<entry>Result</entry>
Minor updates for release.
1999-06-14 09:36:12 +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
</thead>
<tbody>
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><function>trunc</function>(<type>macaddr</type>)</entry>
<entry><type>macaddr</type></entry>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
<entry>set last 3 bytes to zero</entry>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><literal>trunc(macaddr '12:34:56:78:90:ab')</literal></entry>
<entry><literal>12:34:56:00:00:00</literal></entry>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
</row>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</tbody>
</tgroup>
</table>
Convert macaddr documentation to DocBook, update outdated information.
2000-10-04 17:47:45 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The <type>macaddr</type> type also supports the standard relational
operators (<literal>&gt;</literal>, <literal>&lt;=</literal>, etc.) for
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
lexicographical ordering.
</para>
Minor updates for release.
1999-06-14 09:36:12 +02:00
</sect1>
Include new cidr and inet data types.
1998-10-27 07:14:41 +01:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
<sect1 id="functions-sequence">
<title>Sequence-Manipulation Functions</title>
<indexterm>
<primary>sequences</primary>
</indexterm>
<indexterm>
<primary>nextval</primary>
</indexterm>
<indexterm>
<primary>currval</primary>
</indexterm>
<indexterm>
<primary>setval</primary>
</indexterm>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
This section describes <productname>PostgreSQL</productname>'s functions
for operating on <firstterm>sequence objects</firstterm>.
Sequence objects (also called sequence generators or
just sequences) are special single-row tables created with
<command>CREATE SEQUENCE</command>. A sequence object is usually used to
generate unique identifiers for rows of a table. The sequence functions,
listed in <xref linkend="functions-sequence-table">,
provide simple, multiuser-safe methods for obtaining successive
sequence values from sequence objects.
</para>
<table id="functions-sequence-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title>Sequence Functions</title>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
<tgroup cols="3">
<thead>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row><entry>Function</entry> <entry>Returns</entry> <entry>Description</entry></row>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
</thead>
<tbody>
<row>
<entry><function>nextval</function>(<type>text</type>)</entry>
<entry><type>bigint</type></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>Advance sequence and return new value</entry>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
</row>
<row>
<entry><function>currval</function>(<type>text</type>)</entry>
<entry><type>bigint</type></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>Return value most recently obtained with <function>nextval</function></entry>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
</row>
<row>
<entry><function>setval</function>(<type>text</type>,<type>bigint</type>)</entry>
<entry><type>bigint</type></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>Set sequence's current value</entry>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>setval</function>(<type>text</type>,<type>bigint</type>,<type>boolean</type>)</entry>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
<entry><type>bigint</type></entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry>Set sequence's current value and <literal>is_called</literal> flag</entry>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
</row>
</tbody>
</tgroup>
</table>
<para>
For largely historical reasons, the sequence to be operated on by
a sequence-function call is specified by a text-string argument.
To achieve some compatibility with the handling of ordinary SQL
names, the sequence functions convert their argument to lower case
unless the string is double-quoted. Thus
<programlisting>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
nextval('foo') <lineannotation>operates on sequence <literal>foo</literal></>
nextval('FOO') <lineannotation>operates on sequence <literal>foo</literal></>
nextval('"Foo"') <lineannotation>operates on sequence <literal>Foo</literal></>
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
</programlisting>
The sequence name can be schema-qualified if necessary:
<programlisting>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
nextval('myschema.foo') <lineannotation>operates on <literal>myschema.foo</literal></>
nextval('"myschema".foo') <lineannotation>same as above</lineannotation>
nextval('foo') <lineannotation>searches search path for <literal>foo</literal></>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
</programlisting>
Of course, the text argument can be the result of an expression,
not only a simple literal, which is occasionally useful.
</para>
<para>
The available sequence functions are:
<variablelist>
<varlistentry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<term><function>nextval</function></term>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
<listitem>
<para>
Advance the sequence object to its next value and return that
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
value. This is done atomically: even if multiple sessions
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
execute <function>nextval</function> concurrently, each will safely receive
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
a distinct sequence value.
</para>
</listitem>
</varlistentry>
<varlistentry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<term><function>currval</function></term>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
<listitem>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
Return the value most recently obtained by <function>nextval</function>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
for this sequence in the current session. (An error is
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
reported if <function>nextval</function> has never been called for this
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
sequence in this session.) Notice that because this is returning
a session-local value, it gives a predictable answer even if other
sessions are executing <function>nextval</function> meanwhile.
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
</para>
</listitem>
</varlistentry>
<varlistentry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<term><function>setval</function></term>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
<listitem>
<para>
Reset the sequence object's counter value. The two-parameter
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
form sets the sequence's <literal>last_value</literal> field to the specified
value and sets its <literal>is_called</literal> field to <literal>true</literal>,
meaning that the next <function>nextval</function> will advance the sequence
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
before returning a value. In the three-parameter form,
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<literal>is_called</literal> may be set either <literal>true</literal> or
<literal>false</literal>. If it's set to <literal>false</literal>,
the next <function>nextval</function> will return exactly the specified
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
value, and sequence advancement commences with the following
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<function>nextval</function>. For example,
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
<screen>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
SELECT setval('foo', 42); <lineannotation>Next <function>nextval()</> will return 43</lineannotation>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
SELECT setval('foo', 42, true); <lineannotation>Same as above</lineannotation>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
SELECT setval('foo', 42, false); <lineannotation>Next <function>nextval()</> will return 42</lineannotation>
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
</screen>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The result returned by <function>setval</function> is just the value of its
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
second argument.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
<important>
<para>
To avoid blocking of concurrent transactions that obtain numbers from the
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
same sequence, a <function>nextval</function> operation is never rolled back;
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
that is, once a value has been fetched it is considered used, even if the
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
transaction that did the <function>nextval</function> later aborts. This means
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
that aborted transactions may leave unused <quote>holes</quote> in the
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
sequence of assigned values. <function>setval</function> operations are never
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
rolled back, either.
</para>
</important>
<para>
If a sequence object has been created with default parameters,
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<function>nextval()</function> calls on it will return successive values
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
beginning with one. Other behaviors can be obtained by using
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
special parameters in the <command>CREATE SEQUENCE</command> command;
Expand documentation for sequence functions (nextval and friends). Place it in the expected place in the User's Guide, rather than hiding it in the command reference page for CREATE SEQUENCE.
2001-11-17 23:20:34 +01:00
see its command reference page for more information.
</para>
</sect1>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<sect1 id="functions-conditional">
<title>Conditional Expressions</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>case</primary>
</indexterm>
<indexterm>
<primary>conditionals</primary>
</indexterm>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<para>
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
This section describes the <acronym>SQL</acronym>-compliant conditional expressions
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
available in <productname>PostgreSQL</productname>.
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</para>
<tip>
<para>
If your needs go beyond the capabilities of these conditional
expressions you might want to consider writing a stored procedure
in a more expressive programming language.
</para>
</tip>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect2>
<title>CASE</title>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<synopsis>
CASE WHEN <replaceable>condition</replaceable> THEN <replaceable>result</replaceable>
<optional>WHEN ...</optional>
<optional>ELSE <replaceable>result</replaceable></optional>
END
</synopsis>
<para>
The <acronym>SQL</acronym> <token>CASE</token> expression is a
generic conditional expression, similar to if/else statements in
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
other languages. <token>CASE</token> clauses can be used wherever
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
an expression is valid. <replaceable>condition</replaceable> is an
Enhance documentation of date/time functions. Add extract, current_date, current_time, current_timestamp. Add more examples. Remove age(), because it doesn't work like it is documented, and no one could explain it to me.
2001-02-18 18:17:17 +01:00
expression that returns a <type>boolean</type> result. If the result is true
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
then the value of the <token>CASE</token> expression is
<replaceable>result</replaceable>. If the result is false any
subsequent <token>WHEN</token> clauses are searched in the same
manner. If no <token>WHEN</token>
<replaceable>condition</replaceable> is true then the value of the
case expression is the <replaceable>result</replaceable> in the
<token>ELSE</token> clause. If the <token>ELSE</token> clause is
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
omitted and no condition matches, the result is null.
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</para>
<para>
An example:
<screen>
<prompt>=&gt;</prompt> <userinput>SELECT * FROM test;</userinput>
<computeroutput>
a
---
1
2
3
</computeroutput>
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
<prompt>=&gt;</prompt> <userinput>SELECT a,
CASE WHEN a=1 THEN 'one'
WHEN a=2 THEN 'two'
ELSE 'other'
END
FROM test;</userinput>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<computeroutput>
a | case
---+-------
1 | one
2 | two
3 | other
</computeroutput>
</screen>
</para>
<para>
Update type-coercion discussions to reflect current reality.
2000-12-17 06:55:26 +01:00
The data types of all the <replaceable>result</replaceable>
expressions must be coercible to a single output type.
See <xref linkend="typeconv-union-case"> for more detail.
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</para>
<synopsis>
CASE <replaceable>expression</replaceable>
WHEN <replaceable>value</replaceable> THEN <replaceable>result</replaceable>
<optional>WHEN ...</optional>
<optional>ELSE <replaceable>result</replaceable></optional>
END
</synopsis>
<para>
This <quote>simple</quote> <token>CASE</token> expression is a
specialized variant of the general form above. The
<replaceable>expression</replaceable> is computed and compared to
all the <replaceable>value</replaceable>s in the
<token>WHEN</token> clauses until one is found that is equal. If
no match is found, the <replaceable>result</replaceable> in the
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
<token>ELSE</token> clause (or a null value) is returned. This is similar
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
to the <function>switch</function> statement in C.
</para>
<para>
The example above can be written using the simple
<token>CASE</token> syntax:
<screen>
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
<prompt>=&gt;</prompt> <userinput>SELECT a,
CASE a WHEN 1 THEN 'one'
WHEN 2 THEN 'two'
ELSE 'other'
END
FROM test;</userinput>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<computeroutput>
a | case
---+-------
1 | one
2 | two
3 | other
</computeroutput>
</screen>
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</sect2>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect2>
<title>COALESCE</title>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<function>COALESCE</function>(<replaceable>value</replaceable> <optional>, ...</optional>)
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</synopsis>
<para>
The <function>COALESCE</function> function returns the first of its
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
arguments that is not null. This is often useful to substitute a
default value for null values when data is retrieved for display,
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
for example:
<programlisting>
SELECT COALESCE(description, short_description, '(none)') ...
</programlisting>
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</sect2>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect2>
<title>NULLIF</title>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +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>nullif</primary>
</indexterm>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<function>NULLIF</function>(<replaceable>value1</replaceable>, <replaceable>value2</replaceable>)
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</synopsis>
<para>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
The <function>NULLIF</function> function returns a null value if and only
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
if <replaceable>value1</replaceable> and
<replaceable>value2</replaceable> are equal. Otherwise it returns
<replaceable>value1</replaceable>. This can be used to perform the
inverse operation of the <function>COALESCE</function> example
given above:
<programlisting>
SELECT NULLIF(value, '(none)') ...
</programlisting>
</para>
Add note that COALESCE and NULLIF are shorthand forms of CASE.
2000-12-16 19:33:13 +01:00
<tip>
<para>
<function>COALESCE</function> and <function>NULLIF</function> are
just shorthand for <token>CASE</token> expressions. They are actually
converted into <token>CASE</token> expressions at a very early stage
of processing, and subsequent processing thinks it is dealing with
<token>CASE</token>. Thus an incorrect <function>COALESCE</function> or
<function>NULLIF</function> usage may draw an error message that
refers to <token>CASE</token>.
</para>
</tip>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</sect2>
Add note that COALESCE and NULLIF are shorthand forms of CASE.
2000-12-16 19:33:13 +01:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</sect1>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect1 id="functions-misc">
<title>Miscellaneous Functions</title>
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="functions-misc-session-table"> shows several
functions that extract session and system information.
</para>
<table id="functions-misc-session-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title>Session Information Functions</title>
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
<tgroup cols="3">
<thead>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
</thead>
<tbody>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<row>
<entry><function>current_database()</function></entry>
<entry><type>name</type></entry>
<entry>name of current database</entry>
</row>
<row>
<entry><function>current_schema()</function></entry>
<entry><type>name</type></entry>
<entry>name of current schema</entry>
</row>
<row>
<entry><function>current_schemas(boolean)</function></entry>
<entry><type>name[]</type></entry>
<entry>names of schemas in search path optionally including implicit schemas</entry>
</row>
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>current_user</function></entry>
<entry><type>name</type></entry>
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
<entry>user name of current execution context</entry>
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
</row>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>session_user</function></entry>
<entry><type>name</type></entry>
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
<entry>session user name</entry>
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
</row>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>user</function></entry>
<entry><type>name</type></entry>
<entry>equivalent to <function>current_user</function></entry>
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
</row>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
<row>
This minor patch corrects an error in the function docs: it's "version()", not "version". Neil Conway
2002-11-23 05:04:43 +01:00
<entry><function>version()</function></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><type>text</type></entry>
<entry>PostgreSQL version information</entry>
Add current_database(). > Quick system function to pull out the current database. > > I've used this a number of times to allow stored procedures to find out > where they are. Especially useful for those that do logging or hit a > remote server. > > It's called current_database() to match with current_user(). It's also a necessity for an informational schema. The catalog (database) name is required in a number of places. Rod Taylor
2002-08-20 06:46:00 +02:00
</row>
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
</tbody>
</tgroup>
</table>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm zone="functions-misc">
<primary>user</primary>
<secondary>current</secondary>
</indexterm>
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
<indexterm zone="functions-misc">
<primary>schema</primary>
<secondary>current</secondary>
</indexterm>
<indexterm zone="functions-misc">
<primary>search path</primary>
<secondary>current</secondary>
</indexterm>
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The <function>session_user</function> is the user that initiated a
Allow functions to be executed with the privileges of the function owner. I took the opportunity to remove the pg_proc.proistrusted field.
2002-05-18 15:48:01 +02:00
database connection; it is fixed for the duration of that
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
connection. The <function>current_user</function> is the user identifier
Allow functions to be executed with the privileges of the function owner. I took the opportunity to remove the pg_proc.proistrusted field.
2002-05-18 15:48:01 +02:00
that is applicable for permission checking. Normally, it is equal
to the session user, but it changes during the execution of
functions with the attribute <literal>SECURITY DEFINER</literal>.
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
In Unix parlance, the session user is the <quote>real user</quote> and
the current user is the <quote>effective user</quote>.
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
</para>
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
<note>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<function>current_user</function>, <function>session_user</function>, and
<function>user</function> have special syntactic status in <acronym>SQL</acronym>:
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
they must be called without trailing parentheses.
</para>
</note>
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<function>current_schema</function> returns the name of the schema that is
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
at the front of the search path (or a null value if the search path is
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
empty). This is the schema that will be used for any tables or
other named objects that are created without specifying a target schema.
Patch for current_schemas to optionally include implicit ... Second cut attached. This one just adds a boolean option to the existing function to indicate that implicit schemas are to be included (or not). I remembered the docs as well this time :-) Dave Page
2002-06-15 22:03:51 +02:00
<function>current_schemas(boolean)</function> returns an array of the names of all
schemas presently in the search path. The boolean option determines whether or not
implicitly included system schemas such as pg_catalog are included in the search
path returned.
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
</para>
Make link to schema inspection functions more clear.
2002-10-24 23:10:58 +02:00
<para>
> > I had great difficulty in finding how to change the search path, so here > > is a patch to add some cross-referencing. Oliver Elphick
2002-08-22 06:52:17 +02:00
<indexterm>
<primary>search path</primary>
<secondary>changing at runtime</secondary>
</indexterm>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
The search path may be altered by a run-time setting. The
> > I had great difficulty in finding how to change the search path, so here > > is a patch to add some cross-referencing. Oliver Elphick
2002-08-22 06:52:17 +02:00
command to use is <command>
SET SEARCH_PATH '<varname>schema</varname>'[,'<varname>schema</varname>']...
</command>
</para>
Add documentation for pg_get_ruledef and friends.
2001-11-21 23:33:14 +01:00
<indexterm zone="functions-misc">
<primary>version</primary>
</indexterm>
<para>
This minor patch corrects an error in the function docs: it's "version()", not "version". Neil Conway
2002-11-23 05:04:43 +01:00
<function>version()</function> returns a string describing the
<productname>PostgreSQL</productname> server's version.
Add documentation for pg_get_ruledef and friends.
2001-11-21 23:33:14 +01:00
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="functions-misc-set-table"> shows the functions
available to query and alter run-time configuration parameters.
</para>
<table id="functions-misc-set-table">
Here is a doc patch for the SHOW X changes and new config-settings functions. If there are no objections, please apply. Joe Conway
2002-08-04 05:53:11 +02:00
<title>Configuration Settings Information Functions</title>
<tgroup cols="3">
<thead>
<row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
</thead>
<tbody>
<row>
<entry>
<function>current_setting</function>(<parameter>setting_name</parameter>)
</entry>
<entry><type>text</type></entry>
<entry>value of current setting</entry>
</row>
<row>
<entry>
<function>set_config(<parameter>setting_name</parameter>,
<parameter>new_value</parameter>,
<parameter>is_local</parameter>)</function>
</entry>
<entry><type>text</type></entry>
<entry>new value of current setting</entry>
</row>
</tbody>
</tgroup>
</table>
<indexterm zone="functions-misc">
<primary>setting</primary>
<secondary>current</secondary>
</indexterm>
<indexterm zone="functions-misc">
<primary>setting</primary>
<secondary>set</secondary>
</indexterm>
<para>
The <function>current_setting</function> is used to obtain the current
value of the <parameter>setting_name</parameter> setting, as a query
result. It is the equivalent to the SQL <command>SHOW</command> command.
For example:
<programlisting>
select current_setting('DateStyle');
current_setting
---------------------------------------
ISO with US (NonEuropean) conventions
(1 row)
</programlisting>
</para>
<para>
<function>set_config</function> allows the <parameter>setting_name
</parameter> setting to be changed to <parameter>new_value</parameter>.
If <parameter>is_local</parameter> is set to <literal>true</literal>,
the new value will only apply to the current transaction. If you want
the new value to apply for the current session, use
<literal>false</literal> instead. It is the equivalent to the SQL
<command>SET</command> command. For example:
<programlisting>
Add log_duration to GUC/postgresql.conf. Rename debug_print_query to log_statement and rename show_query_stats to show_statement_stats.
2002-09-02 01:26:06 +02:00
select set_config('show_statement_stats','off','f');
Here is a doc patch for the SHOW X changes and new config-settings functions. If there are no objections, please apply. Joe Conway
2002-08-04 05:53:11 +02:00
set_config
------------
off
(1 row)
</programlisting>
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="functions-misc-access-table"> lists functions that
allow the user to query object access privileges programmatically.
See <xref linkend="ddl-priv"> for more information about
privileges.
</para>
<table id="functions-misc-access-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title>Access Privilege Inquiry Functions</title>
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
<tgroup cols="3">
<thead>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
</thead>
<tbody>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>has_table_privilege</function>(<parameter>user</parameter>,
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
<parameter>table</parameter>,
<parameter>access</parameter>)
</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><type>boolean</type></entry>
<entry>does user have access to table</entry>
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
</row>
<row>
Markup additions and spell check. (covers User's Guide)
2001-09-09 19:21:59 +02:00
<entry><function>has_table_privilege</function>(<parameter>table</parameter>,
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
<parameter>access</parameter>)
</entry>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><type>boolean</type></entry>
<entry>does current user have access to table</entry>
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
</row>
has_table_privilege spawns scions has_database_privilege, has_function_privilege, has_language_privilege, has_schema_privilege to let SQL queries test all the new privilege types in 7.3. Also, add functions pg_table_is_visible, pg_type_is_visible, pg_function_is_visible, pg_operator_is_visible, pg_opclass_is_visible to test whether objects contained in schemas are visible in the current search path. Do some minor cleanup to centralize accesses to pg_database, as well.
2002-08-09 18:45:16 +02:00
<row>
<entry><function>has_database_privilege</function>(<parameter>user</parameter>,
<parameter>database</parameter>,
<parameter>access</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>does user have access to database</entry>
</row>
<row>
<entry><function>has_database_privilege</function>(<parameter>database</parameter>,
<parameter>access</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>does current user have access to database</entry>
</row>
<row>
<entry><function>has_function_privilege</function>(<parameter>user</parameter>,
<parameter>function</parameter>,
<parameter>access</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>does user have access to function</entry>
</row>
<row>
<entry><function>has_function_privilege</function>(<parameter>function</parameter>,
<parameter>access</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>does current user have access to function</entry>
</row>
<row>
<entry><function>has_language_privilege</function>(<parameter>user</parameter>,
<parameter>language</parameter>,
<parameter>access</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>does user have access to language</entry>
</row>
<row>
<entry><function>has_language_privilege</function>(<parameter>language</parameter>,
<parameter>access</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>does current user have access to language</entry>
</row>
<row>
<entry><function>has_schema_privilege</function>(<parameter>user</parameter>,
<parameter>schema</parameter>,
<parameter>access</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>does user have access to schema</entry>
</row>
<row>
<entry><function>has_schema_privilege</function>(<parameter>schema</parameter>,
<parameter>access</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>does current user have access to schema</entry>
</row>
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
</tbody>
</tgroup>
</table>
<indexterm zone="functions-misc">
<primary>has_table_privilege</primary>
</indexterm>
has_table_privilege spawns scions has_database_privilege, has_function_privilege, has_language_privilege, has_schema_privilege to let SQL queries test all the new privilege types in 7.3. Also, add functions pg_table_is_visible, pg_type_is_visible, pg_function_is_visible, pg_operator_is_visible, pg_opclass_is_visible to test whether objects contained in schemas are visible in the current search path. Do some minor cleanup to centralize accesses to pg_database, as well.
2002-08-09 18:45:16 +02:00
<indexterm zone="functions-misc">
<primary>has_database_privilege</primary>
</indexterm>
<indexterm zone="functions-misc">
<primary>has_function_privilege</primary>
</indexterm>
<indexterm zone="functions-misc">
<primary>has_language_privilege</primary>
</indexterm>
<indexterm zone="functions-misc">
<primary>has_schema_privilege</primary>
</indexterm>
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
<para>
has_table_privilege spawns scions has_database_privilege, has_function_privilege, has_language_privilege, has_schema_privilege to let SQL queries test all the new privilege types in 7.3. Also, add functions pg_table_is_visible, pg_type_is_visible, pg_function_is_visible, pg_operator_is_visible, pg_opclass_is_visible to test whether objects contained in schemas are visible in the current search path. Do some minor cleanup to centralize accesses to pg_database, as well.
2002-08-09 18:45:16 +02:00
<function>has_table_privilege</function> checks whether a user
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
can access a table in a particular way. The user can be
Add documentation for pg_get_ruledef and friends.
2001-11-21 23:33:14 +01:00
specified by name or by ID
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
(<classname>pg_user</classname>.<structfield>usesysid</structfield>), or if the argument is
Add documentation for pg_get_ruledef and friends.
2001-11-21 23:33:14 +01:00
omitted
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<function>current_user</function> is assumed. The table can be specified
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
by name or by OID. (Thus, there are actually six variants of
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<function>has_table_privilege</function>, which can be distinguished by
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
the number and types of their arguments.) When specifying by name,
the name can be schema-qualified if necessary.
The desired access type
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
is specified by a text string, which must evaluate to one of the
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
values <literal>SELECT</literal>, <literal>INSERT</literal>, <literal>UPDATE</literal>,
<literal>DELETE</literal>, <literal>RULE</literal>, <literal>REFERENCES</literal>, or
<literal>TRIGGER</literal>. (Case of the string is not significant, however.)
Add current_schema() and current_schemas() inquiry functions. Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
2002-04-26 03:24:08 +02:00
An example is:
<programlisting>
SELECT has_table_privilege('myschema.mytable', 'select');
</programlisting>
Oops, forgot to commit doco updates for has_table_privilege.
2001-06-15 23:03:07 +02:00
</para>
has_table_privilege spawns scions has_database_privilege, has_function_privilege, has_language_privilege, has_schema_privilege to let SQL queries test all the new privilege types in 7.3. Also, add functions pg_table_is_visible, pg_type_is_visible, pg_function_is_visible, pg_operator_is_visible, pg_opclass_is_visible to test whether objects contained in schemas are visible in the current search path. Do some minor cleanup to centralize accesses to pg_database, as well.
2002-08-09 18:45:16 +02:00
<para>
<function>has_database_privilege</function> checks whether a user
can access a database in a particular way. The possibilities for its
arguments are analogous to <function>has_table_privilege</function>.
The desired access type must evaluate to
<literal>CREATE</literal>,
<literal>TEMPORARY</literal>, or
<literal>TEMP</literal> (which is equivalent to
<literal>TEMPORARY</literal>).
</para>
<para>
<function>has_function_privilege</function> checks whether a user
can access a function in a particular way. The possibilities for its
arguments are analogous to <function>has_table_privilege</function>.
When specifying a function by a text string rather than by OID,
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
the allowed input is the same as for the <type>regprocedure</> data type.
has_table_privilege spawns scions has_database_privilege, has_function_privilege, has_language_privilege, has_schema_privilege to let SQL queries test all the new privilege types in 7.3. Also, add functions pg_table_is_visible, pg_type_is_visible, pg_function_is_visible, pg_operator_is_visible, pg_opclass_is_visible to test whether objects contained in schemas are visible in the current search path. Do some minor cleanup to centralize accesses to pg_database, as well.
2002-08-09 18:45:16 +02:00
The desired access type must currently evaluate to
<literal>EXECUTE</literal>.
</para>
<para>
<function>has_language_privilege</function> checks whether a user
can access a procedural language in a particular way. The possibilities
for its arguments are analogous to <function>has_table_privilege</function>.
The desired access type must currently evaluate to
<literal>USAGE</literal>.
</para>
<para>
<function>has_schema_privilege</function> checks whether a user
can access a schema in a particular way. The possibilities for its
arguments are analogous to <function>has_table_privilege</function>.
The desired access type must evaluate to
<literal>CREATE</literal> or
<literal>USAGE</literal>.
</para>
Grant options, and cascading revoke. Grant options are allowed only for users right now, not groups. Extension of has_foo_privileges functions to query the grant options. Extension of aclitem type to store grantor.
2003-01-24 00:39:07 +01:00
<para>
To evaluate whether a user holds a grant option on the privilege,
append <literal> WITH GRANT OPTION</literal> to the privilege key
word; for example <literal>'UPDATE WITH GRANT OPTION'</literal>.
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<para>
<xref linkend="functions-misc-schema-table"> shows functions that
determine whether a certain object is <firstterm>visible</> in the
current schema search path. A table is said to be visible if its
containing schema is in the search path and no table of the same
name appears earlier in the search path. This is equivalent to the
statement that the table can be referenced by name without explicit
schema qualification. For example, to list the names of all
visible tables:
<programlisting>
SELECT relname FROM pg_class WHERE pg_table_is_visible(oid);
</programlisting>
</para>
<table id="functions-misc-schema-table">
has_table_privilege spawns scions has_database_privilege, has_function_privilege, has_language_privilege, has_schema_privilege to let SQL queries test all the new privilege types in 7.3. Also, add functions pg_table_is_visible, pg_type_is_visible, pg_function_is_visible, pg_operator_is_visible, pg_opclass_is_visible to test whether objects contained in schemas are visible in the current search path. Do some minor cleanup to centralize accesses to pg_database, as well.
2002-08-09 18:45:16 +02:00
<title>Schema Visibility Inquiry Functions</title>
<tgroup cols="3">
<thead>
<row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
</thead>
<tbody>
<row>
<entry><function>pg_table_is_visible</function>(<parameter>tableOID</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>is table visible in search path</entry>
</row>
<row>
<entry><function>pg_type_is_visible</function>(<parameter>typeOID</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>is type visible in search path</entry>
</row>
<row>
<entry><function>pg_function_is_visible</function>(<parameter>functionOID</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>is function visible in search path</entry>
</row>
<row>
<entry><function>pg_operator_is_visible</function>(<parameter>operatorOID</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>is operator visible in search path</entry>
</row>
<row>
<entry><function>pg_opclass_is_visible</function>(<parameter>opclassOID</parameter>)
</entry>
<entry><type>boolean</type></entry>
<entry>is operator class visible in search path</entry>
</row>
</tbody>
</tgroup>
</table>
<indexterm zone="functions-misc">
<primary>pg_table_is_visible</primary>
</indexterm>
<indexterm zone="functions-misc">
<primary>pg_type_is_visible</primary>
</indexterm>
<indexterm zone="functions-misc">
<primary>pg_function_is_visible</primary>
</indexterm>
<indexterm zone="functions-misc">
<primary>pg_operator_is_visible</primary>
</indexterm>
<indexterm zone="functions-misc">
<primary>pg_opclass_is_visible</primary>
</indexterm>
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<function>pg_table_is_visible</function> performs the check for
tables (or views, or any other kind of <literal>pg_class</> entry).
<function>pg_type_is_visible</function>,
<function>pg_function_is_visible</function>,
<function>pg_operator_is_visible</function>, and
<function>pg_opclass_is_visible</function> perform the same sort of
visibility check for types, functions, operators, and operator
classes, respectively. For functions and operators, an object in
the search path is visible if there is no object of the same name
<emphasis>and argument data type(s)</> earlier in the path. For
operator classes, both name and associated index access method are
considered.
has_table_privilege spawns scions has_database_privilege, has_function_privilege, has_language_privilege, has_schema_privilege to let SQL queries test all the new privilege types in 7.3. Also, add functions pg_table_is_visible, pg_type_is_visible, pg_function_is_visible, pg_operator_is_visible, pg_opclass_is_visible to test whether objects contained in schemas are visible in the current search path. Do some minor cleanup to centralize accesses to pg_database, as well.
2002-08-09 18:45:16 +02:00
</para>
<para>
All these functions require object OIDs to identify the object to be
checked. If you want to test an object by name, it is convenient to use
the OID alias types (<type>regclass</>, <type>regtype</>,
<type>regprocedure</>, or <type>regoperator</>), for example
<programlisting>
SELECT pg_type_is_visible('myschema.widget'::regtype);
</programlisting>
Note that it would not make much sense to test an unqualified name in
this way --- if the name can be recognized at all, it must be visible.
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<indexterm zone="functions-misc">
<primary>pg_get_viewdef</primary>
</indexterm>
<indexterm zone="functions-misc">
<primary>pg_get_ruledef</primary>
</indexterm>
<indexterm zone="functions-misc">
<primary>pg_get_indexdef</primary>
</indexterm>
<indexterm zone="functions-misc">
<primary>pg_get_constraintdef</primary>
</indexterm>
<indexterm zone="functions-misc">
<primary>pg_get_userbyid</primary>
</indexterm>
<para>
<xref linkend="functions-misc-catalog-table"> lists functions that
extract information from the system catalogs.
<function>pg_get_viewdef()</function>,
<function>pg_get_ruledef()</function>,
<function>pg_get_indexdef()</function>, and
<function>pg_get_constraintdef()</function> respectively
reconstruct the creating command for a view, rule, index, or
constraint. (Note that this is a decompiled reconstruction, not
the verbatim text of the command.) At present
<function>pg_get_constraintdef()</function> only works for
foreign-key constraints. <function>pg_get_userbyid()</function>
extracts a user's name given a <structfield>usesysid</structfield>
value.
</para>
<table id="functions-misc-catalog-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title>Catalog Information Functions</title>
A bunch of small doco updates motivated by scanning the comments on the interactive docs.
2001-11-19 04:58:25 +01:00
<tgroup cols="3">
<thead>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
A bunch of small doco updates motivated by scanning the comments on the interactive docs.
2001-11-19 04:58:25 +01:00
</thead>
<tbody>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>pg_get_viewdef</function>(<parameter>viewname</parameter>)</entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Get <command>CREATE VIEW</> command for view (<emphasis>deprecated</emphasis>)</entry>
Add documentation for pg_get_ruledef and friends.
2001-11-21 23:33:14 +01:00
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>pg_get_viewdef</function>(<parameter>viewOID</parameter>)</entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Get <command>CREATE VIEW</> command for view</entry>
Rule names are now unique per-relation, rather than unique globally. DROP RULE and COMMENT ON RULE syntax adds an 'ON tablename' clause, similar to TRIGGER syntaxes. To allow loading of existing pg_dump files containing COMMENT ON RULE, the COMMENT code will still accept the old syntax --- but only if the target rulename is unique across the whole database.
2002-04-18 22:01:11 +02:00
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>pg_get_ruledef</function>(<parameter>ruleOID</parameter>)</entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Get <command>CREATE RULE</> command for rule</entry>
Add documentation for pg_get_ruledef and friends.
2001-11-21 23:33:14 +01:00
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>pg_get_indexdef</function>(<parameter>indexOID</parameter>)</entry>
<entry><type>text</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Get <command>CREATE INDEX</> command for index</entry>
Add documentation for pg_get_ruledef and friends.
2001-11-21 23:33:14 +01:00
</row>
Modify pg_dump to dump foreign-key constraints as constraints, not as sets of triggers. Also modify psql \d command to show foreign key constraints as such and hide the triggers. pg_get_constraintdef() function added to backend to support these. From Rod Taylor, code review and some editorialization by Tom Lane.
2002-08-17 01:01:21 +02:00
<row>
<entry><function>pg_get_constraintdef</function>(<parameter>constraintOID</parameter>)</entry>
<entry><type>text</type></entry>
<entry>Get definition of a constraint</entry>
</row>
Add documentation for pg_get_ruledef and friends.
2001-11-21 23:33:14 +01:00
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>pg_get_userbyid</function>(<parameter>userid</parameter>)</entry>
<entry><type>name</type></entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Get user name with given ID</entry>
A bunch of small doco updates motivated by scanning the comments on the interactive docs.
2001-11-19 04:58:25 +01:00
</row>
</tbody>
</tgroup>
</table>
<indexterm zone="functions-misc">
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<primary>obj_description</primary>
Modify pg_dump to dump foreign-key constraints as constraints, not as sets of triggers. Also modify psql \d command to show foreign key constraints as such and hide the triggers. pg_get_constraintdef() function added to backend to support these. From Rod Taylor, code review and some editorialization by Tom Lane.
2002-08-17 01:01:21 +02:00
</indexterm>
Add documentation for pg_get_ruledef and friends.
2001-11-21 23:33:14 +01:00
<indexterm zone="functions-misc">
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<primary>col_description</primary>
A bunch of small doco updates motivated by scanning the comments on the interactive docs.
2001-11-19 04:58:25 +01:00
</indexterm>
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The function shown in <xref
linkend="functions-misc-comment-table"> extract comments
previously stored with the <command>COMMENT</command> command. A
null value is returned if no comment can be found matching the
specified parameters.
A bunch of small doco updates motivated by scanning the comments on the interactive docs.
2001-11-19 04:58:25 +01:00
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table id="functions-misc-comment-table">
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<title>Comment Information Functions</title>
Document obj_description and col_description functions; expand description of COMMENT command.
2001-12-27 22:36:57 +01:00
<tgroup cols="3">
<thead>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
Document obj_description and col_description functions; expand description of COMMENT command.
2001-12-27 22:36:57 +01:00
</thead>
<tbody>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>obj_description</function>(<parameter>objectOID</parameter>, <parameter>tablename</parameter>)</entry>
<entry><type>text</type></entry>
<entry>Get comment for a database object</entry>
Document obj_description and col_description functions; expand description of COMMENT command.
2001-12-27 22:36:57 +01:00
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>obj_description</function>(<parameter>objectOID</parameter>)</entry>
<entry><type>text</type></entry>
<entry>Get comment for a database object (<emphasis>deprecated</emphasis>)</entry>
Document obj_description and col_description functions; expand description of COMMENT command.
2001-12-27 22:36:57 +01:00
</row>
<row>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<entry><function>col_description</function>(<parameter>tableOID</parameter>, <parameter>columnnumber</parameter>)</entry>
<entry><type>text</type></entry>
<entry>Get comment for a table column</entry>
Document obj_description and col_description functions; expand description of COMMENT command.
2001-12-27 22:36:57 +01:00
</row>
</tbody>
</tgroup>
</table>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The two-parameter form of <function>obj_description()</function> returns the
Document obj_description and col_description functions; expand description of COMMENT command.
2001-12-27 22:36:57 +01:00
comment for a database object specified by its OID and the name of the
containing system catalog. For example,
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<literal>obj_description(123456,'pg_class')</literal>
Document obj_description and col_description functions; expand description of COMMENT command.
2001-12-27 22:36:57 +01:00
would retrieve the comment for a table with OID 123456.
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The one-parameter form of <function>obj_description()</function> requires only
Document obj_description and col_description functions; expand description of COMMENT command.
2001-12-27 22:36:57 +01:00
the object OID. It is now deprecated since there is no guarantee that
OIDs are unique across different system catalogs; therefore, the wrong
comment could be returned.
</para>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<function>col_description()</function> returns the comment for a table column,
Document obj_description and col_description functions; expand description of COMMENT command.
2001-12-27 22:36:57 +01:00
which is specified by the OID of its table and its column number.
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<function>obj_description()</function> cannot be used for table columns since
Document obj_description and col_description functions; expand description of COMMENT command.
2001-12-27 22:36:57 +01:00
columns do not have OIDs of their own.
</para>
Implement differentiation between CURRENT_USER and SESSION_USER as per SQL. There is still no effective difference but it will kick in once setuid functions exist (not included here). Make old getpgusername() alias for current_user.
2000-09-19 20:18:04 +02:00
</sect1>
> Great! Please cc: the docs or hackers mailing lists to make sure the > patches are not lost... Aggregate doc patches: The patches are attached. Be great if you could check them over to make sure all relevant content (and markup) is there... Isaac Wilcox
2000-06-20 20:04:18 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<sect1 id="functions-aggregate">
<title>Aggregate Functions</title>
> Great! Please cc: the docs or hackers mailing lists to make sure the > patches are not lost... Aggregate doc patches: The patches are attached. Be great if you could check them over to make sure all relevant content (and markup) is there... Isaac Wilcox
2000-06-20 20:04:18 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<para>
<firstterm>Aggregate functions</firstterm> compute a single result
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
value from a set of input values. <xref
linkend="functions-aggregate-table"> show the built-in aggregate
functions. The special syntax considerations for aggregate
functions are explained in <xref linkend="syntax-aggregates">.
Consult the &cite-tutorial; for additional introductory
information.
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</para>
Update aggregate-function docs for STDDEV, VARIANCE.
2000-07-17 05:52:28 +02:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<table id="functions-aggregate-table">
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<title>Aggregate Functions</title>
Update aggregate-function docs for STDDEV, VARIANCE.
2000-07-17 05:52:28 +02:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<tgroup cols="5">
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<thead>
<row>
<entry>Function</entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>Argument Type</entry>
<entry>Return Type</entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>average</primary>
<secondary>function</secondary>
</indexterm>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<function>avg(<replaceable class="parameter">expression</replaceable>)</function>
</entry>
<entry>
<type>smallint</type>, <type>integer</type>,
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<type>bigint</type>, <type>real</type>, <type>double
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
precision</type>, <type>numeric</type>, or <type>interval</type>.
</entry>
<entry>
<type>numeric</type> for any integer type argument,
<type>double precision</type> for a floating-point argument,
otherwise the same as the argument data type
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>the average (arithmetic mean) of all input values</entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
<row>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><function>count(*)</function></entry>
<entry></entry>
<entry><type>bigint</type></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>number of input values</entry>
</row>
<row>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><function>count(<replaceable class="parameter">expression</replaceable>)</function></entry>
<entry>any</entry>
<entry><type>bigint</type></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
number of input values for which the value of <replaceable
class="parameter">expression</replaceable> is not null
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</entry>
</row>
<row>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><function>max(<replaceable class="parameter">expression</replaceable>)</function></entry>
<entry>any numeric, string, or date/time type</entry>
<entry>same as argument type</entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
maximum value of <replaceable
class="parameter">expression</replaceable> across all input
values
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</entry>
</row>
<row>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><function>min(<replaceable class="parameter">expression</replaceable>)</function></entry>
<entry>any numeric, string, or date/time type</entry>
<entry>same as argument type</entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
minimum value of <replaceable
class="parameter">expression</replaceable> across all input
values
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</entry>
</row>
<row>
<entry>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>standard deviation</primary>
</indexterm>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<function>stddev(<replaceable class="parameter">expression</replaceable>)</function>
</entry>
<entry>
<type>smallint</type>, <type>integer</type>,
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<type>bigint</type>, <type>real</type>, <type>double
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
precision</type>, or <type>numeric</type>.
</entry>
<entry>
<type>double precision</type> for floating-point arguments,
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
otherwise <type>numeric</type>.
</entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>sample standard deviation of the input values</entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
<row>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry><function>sum(<replaceable class="parameter">expression</replaceable>)</function></entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<entry>
<type>smallint</type>, <type>integer</type>,
<type>bigint</type>, <type>real</type>, <type>double
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
precision</type>, <type>numeric</type>, or
<type>interval</type>
</entry>
<entry>
<type>bigint</type> for <type>smallint</type> or
<type>integer</type> arguments, <type>numeric</type> for
<type>bigint</type> arguments, <type>double precision</type>
for floating-point arguments, otherwise the same as the
argument data type
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>sum of <replaceable class="parameter">expression</replaceable> across all input values</entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
<row>
<entry>
Add index. Only some parts of the manual set have index entries so far...
2001-05-13 00:51:36 +02:00
<indexterm>
<primary>variance</primary>
</indexterm>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<function>variance</function>(<replaceable class="parameter">expression</replaceable>)
</entry>
<entry>
<type>smallint</type>, <type>integer</type>,
<type>bigint</type>, <type>real</type>, <type>double
precision</type>, or <type>numeric</type>.
</entry>
<entry>
<type>double precision</type> for floating-point arguments,
otherwise <type>numeric</type>.
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</entry>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<entry>sample variance of the input values (square of the sample standard deviation)</entry>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</row>
</tbody>
</tgroup>
</table>
Update aggregate-function docs for STDDEV, VARIANCE.
2000-07-17 05:52:28 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
It should be noted that except for <function>count</function>,
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
these functions return a null value when no rows are selected. In
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
particular, <function>sum</function> of no rows returns null, not
zero as one might expect. The function <function>coalesce</function> may be
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
used to substitute zero for null when necessary.
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</para>
Update aggregate-function docs for STDDEV, VARIANCE.
2000-07-17 05:52:28 +02:00
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</sect1>
Update aggregate-function docs for STDDEV, VARIANCE.
2000-07-17 05:52:28 +02:00
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<sect1 id="functions-subquery">
<title>Subquery Expressions</title>
<indexterm>
<primary>exists</primary>
</indexterm>
<indexterm>
<primary>in</primary>
</indexterm>
<indexterm>
<primary>not in</primary>
</indexterm>
<indexterm>
<primary>any</primary>
</indexterm>
<indexterm>
<primary>all</primary>
</indexterm>
<indexterm>
<primary>some</primary>
</indexterm>
<indexterm>
<primary>subqueries</primary>
</indexterm>
<para>
This section describes the <acronym>SQL</acronym>-compliant subquery
expressions available in <productname>PostgreSQL</productname>.
All of the expression forms documented in this section return
Boolean (true/false) results.
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect2>
<title>EXISTS</title>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<synopsis>
EXISTS ( <replaceable>subquery</replaceable> )
</synopsis>
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The argument of <token>EXISTS</token> is an arbitrary <command>SELECT</> statement,
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
or <firstterm>subquery</firstterm>. The
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
subquery is evaluated to determine whether it returns any rows.
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
If it returns at least one row, the result of <token>EXISTS</token> is
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<quote>true</>; if the subquery returns no rows, the result of <token>EXISTS</token>
is <quote>false</>.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
The subquery can refer to variables from the surrounding query,
which will act as constants during any one evaluation of the subquery.
</para>
<para>
The subquery will generally only be executed far enough to determine
whether at least one row is returned, not all the way to completion.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
It is unwise to write a subquery that has any side effects (such as
calling sequence functions); whether the side effects occur or not
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
may be difficult to predict.
</para>
<para>
Since the result depends only on whether any rows are returned,
and not on the contents of those rows, the output list of the
subquery is normally uninteresting. A common coding convention is
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
to write all <literal>EXISTS</> tests in the form
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<literal>EXISTS(SELECT 1 WHERE ...)</literal>. There are exceptions to
this rule however, such as subqueries that use <token>INTERSECT</token>.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
This simple example is like an inner join on <literal>col2</>, but
it produces at most one output row for each <literal>tab1</> row,
even if there are multiple matching <literal>tab2</> rows:
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<screen>
SELECT col1 FROM tab1
WHERE EXISTS(SELECT 1 FROM tab2 WHERE col2 = tab1.col2);
</screen>
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</sect2>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect2>
<title>IN (scalar form)</title>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<replaceable>expression</replaceable> IN (<replaceable>value</replaceable><optional>, ...</optional>)
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</synopsis>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The right-hand side of this form of <token>IN</token> is a parenthesized list
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
of scalar expressions. The result is <quote>true</> if the left-hand expression's
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
result is equal to any of the right-hand expressions. This is a shorthand
notation for
<synopsis>
<replaceable>expression</replaceable> = <replaceable>value1</replaceable>
OR
<replaceable>expression</replaceable> = <replaceable>value2</replaceable>
OR
...
</synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Note that if the left-hand expression yields null, or if there are
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
no equal right-hand values and at least one right-hand expression yields
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
null, the result of the <token>IN</token> construct will be null, not false.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
This is in accordance with SQL's normal rules for Boolean combinations
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
of null values.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<note>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
This form of <token>IN</token> is not truly a subquery expression, but it
seems best to document it in the same place as subquery <token>IN</token>.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
</note>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</sect2>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect2>
<title>IN (subquery form)</title>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<synopsis>
<replaceable>expression</replaceable> IN (<replaceable>subquery</replaceable>)
</synopsis>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The right-hand side of this form of <token>IN</token> is a parenthesized
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
subquery, which must return exactly one column. The left-hand expression
is evaluated and compared to each row of the subquery result.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result of <token>IN</token> is <quote>true</> if any equal subquery row is found.
The result is <quote>false</> if no equal row is found (including the special
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
case where the subquery returns no rows).
</para>
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Note that if the left-hand expression yields null, or if there are
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
no equal right-hand values and at least one right-hand row yields
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
null, the result of the <token>IN</token> construct will be null, not false.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
This is in accordance with SQL's normal rules for Boolean combinations
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
of null values.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
As with <token>EXISTS</token>, it's unwise to assume that the subquery will
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
be evaluated completely.
</para>
<synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
(<replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ...</optional>) IN (<replaceable>subquery</replaceable>)
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</synopsis>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The right-hand side of this form of <token>IN</token> is a parenthesized
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
subquery, which must return exactly as many columns as there are
expressions in the left-hand list. The left-hand expressions are
evaluated and compared row-wise to each row of the subquery result.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result of <token>IN</token> is <quote>true</> if any equal subquery row is found.
The result is <quote>false</> if no equal row is found (including the special
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
case where the subquery returns no rows).
</para>
<para>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
As usual, null values in the expressions or subquery rows are combined per
Spell-check and markup police
2002-01-20 23:19:57 +01:00
the normal rules of SQL Boolean expressions. Two rows are considered
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
equal if all their corresponding members are non-null and equal; the rows
are unequal if any corresponding members are non-null and unequal;
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
otherwise the result of that row comparison is unknown (null).
If all the row results are either unequal or null, with at least one null,
then the result of <token>IN</token> is null.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</sect2>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect2>
<title>NOT IN (scalar form)</title>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<replaceable>expression</replaceable> NOT IN (<replaceable>value</replaceable><optional>, ...</optional>)
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</synopsis>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The right-hand side of this form of <token>NOT IN</token> is a parenthesized list
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
of scalar expressions. The result is <quote>true</quote> if the left-hand expression's
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
result is unequal to all of the right-hand expressions. This is a shorthand
notation for
<synopsis>
<replaceable>expression</replaceable> &lt;&gt; <replaceable>value1</replaceable>
AND
<replaceable>expression</replaceable> &lt;&gt; <replaceable>value2</replaceable>
AND
...
</synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Note that if the left-hand expression yields null, or if there are
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
no equal right-hand values and at least one right-hand expression yields
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
null, the result of the <token>NOT IN</token> construct will be null, not true
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
as one might naively expect.
This is in accordance with SQL's normal rules for Boolean combinations
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
of null values.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<tip>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<literal>x NOT IN y</literal> is equivalent to <literal>NOT (x IN y)</literal> in all
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
cases. However, null values are much more likely to trip up the novice when
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
working with <token>NOT IN</token> than when working with <token>IN</token>.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
It's best to express your condition positively if possible.
</para>
</tip>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</sect2>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect2>
<title>NOT IN (subquery form)</title>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<synopsis>
<replaceable>expression</replaceable> NOT IN (<replaceable>subquery</replaceable>)
</synopsis>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The right-hand side of this form of <token>NOT IN</token> is a parenthesized
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
subquery, which must return exactly one column. The left-hand expression
is evaluated and compared to each row of the subquery result.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result of <token>NOT IN</token> is <quote>true</> if only unequal subquery rows
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
are found (including the special case where the subquery returns no rows).
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result is <quote>false</> if any equal row is found.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
Note that if the left-hand expression yields null, or if there are
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
no equal right-hand values and at least one right-hand row yields
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
null, the result of the <token>NOT IN</token> construct will be null, not true.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
This is in accordance with SQL's normal rules for Boolean combinations
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
of null values.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
As with <token>EXISTS</token>, it's unwise to assume that the subquery will
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
be evaluated completely.
</para>
<synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
(<replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ...</optional>) NOT IN (<replaceable>subquery</replaceable>)
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</synopsis>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The right-hand side of this form of <token>NOT IN</token> is a parenthesized
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
subquery, which must return exactly as many columns as there are
expressions in the left-hand list. The left-hand expressions are
evaluated and compared row-wise to each row of the subquery result.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result of <token>NOT IN</token> is <quote>true</> if only unequal subquery rows
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
are found (including the special case where the subquery returns no rows).
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result is <quote>false</> if any equal row is found.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
As usual, null values in the expressions or subquery rows are combined per
Spell-check and markup police
2002-01-20 23:19:57 +01:00
the normal rules of SQL Boolean expressions. Two rows are considered
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
equal if all their corresponding members are non-null and equal; the rows
are unequal if any corresponding members are non-null and unequal;
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
otherwise the result of that row comparison is unknown (null).
If all the row results are either unequal or null, with at least one null,
then the result of <token>NOT IN</token> is null.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</sect2>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect2>
<title>ANY/SOME</title>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<replaceable>expression</replaceable> <replaceable>operator</replaceable> ANY (<replaceable>subquery</replaceable>)
<replaceable>expression</replaceable> <replaceable>operator</replaceable> SOME (<replaceable>subquery</replaceable>)
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</synopsis>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The right-hand side of this form of <token>ANY</token> is a parenthesized
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
subquery, which must return exactly one column. The left-hand expression
is evaluated and compared to each row of the subquery result using the
Spell-check and markup police
2002-01-20 23:19:57 +01:00
given <replaceable>operator</replaceable>, which must yield a Boolean
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
result.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result of <token>ANY</token> is <quote>true</> if any true result is obtained.
The result is <quote>false</> if no true result is found (including the special
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
case where the subquery returns no rows).
</para>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<token>SOME</token> is a synonym for <token>ANY</token>.
<token>IN</token> is equivalent to <literal>= ANY</literal>.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
Note that if there are no successes and at least one right-hand row yields
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
null for the operator's result, the result of the <token>ANY</token> construct
will be null, not false.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
This is in accordance with SQL's normal rules for Boolean combinations
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
of null values.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
As with <token>EXISTS</token>, it's unwise to assume that the subquery will
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
be evaluated completely.
</para>
<synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
(<replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ...</optional>) <replaceable>operator</> ANY (<replaceable>subquery</replaceable>)
(<replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ...</optional>) <replaceable>operator</> SOME (<replaceable>subquery</replaceable>)
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</synopsis>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The right-hand side of this form of <token>ANY</token> is a parenthesized
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
subquery, which must return exactly as many columns as there are
expressions in the left-hand list. The left-hand expressions are
evaluated and compared row-wise to each row of the subquery result,
using the given <replaceable>operator</replaceable>. Presently,
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
only <literal>=</literal> and <literal>&lt;&gt;</literal> operators are allowed
in row-wise <token>ANY</token> queries.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result of <token>ANY</token> is <quote>true</> if any equal or unequal row is
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
found, respectively.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result is <quote>false</> if no such row is found (including the special
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
case where the subquery returns no rows).
</para>
<para>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
As usual, null values in the expressions or subquery rows are combined per
Spell-check and markup police
2002-01-20 23:19:57 +01:00
the normal rules of SQL Boolean expressions. Two rows are considered
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
equal if all their corresponding members are non-null and equal; the rows
are unequal if any corresponding members are non-null and unequal;
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
otherwise the result of that row comparison is unknown (null).
If there is at least one null row result, then the result of <token>ANY</token>
cannot be false; it will be true or null.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</sect2>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect2>
<title>ALL</title>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<replaceable>expression</replaceable> <replaceable>operator</replaceable> ALL (<replaceable>subquery</replaceable>)
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</synopsis>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The right-hand side of this form of <token>ALL</token> is a parenthesized
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
subquery, which must return exactly one column. The left-hand expression
is evaluated and compared to each row of the subquery result using the
Spell-check and markup police
2002-01-20 23:19:57 +01:00
given <replaceable>operator</replaceable>, which must yield a Boolean
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
result.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result of <token>ALL</token> is <quote>true</> if all rows yield true
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
(including the special case where the subquery returns no rows).
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result is <quote>false</> if any false result is found.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<token>NOT IN</token> is equivalent to <literal>&lt;&gt; ALL</literal>.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
Note that if there are no failures but at least one right-hand row yields
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
null for the operator's result, the result of the <token>ALL</token> construct
will be null, not true.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
This is in accordance with SQL's normal rules for Boolean combinations
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
of null values.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
As with <token>EXISTS</token>, it's unwise to assume that the subquery will
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
be evaluated completely.
</para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
(<replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ...</optional>) <replaceable>operator</replaceable> ALL (<replaceable>subquery</replaceable>)
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</synopsis>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<para>
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
The right-hand side of this form of <token>ALL</token> is a parenthesized
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
subquery, which must return exactly as many columns as there are
expressions in the left-hand list. The left-hand expressions are
evaluated and compared row-wise to each row of the subquery result,
using the given <replaceable>operator</replaceable>. Presently,
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
only <literal>=</literal> and <literal>&lt;&gt;</literal> operators are allowed
in row-wise <token>ALL</token> queries.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result of <token>ALL</token> is <quote>true</> if all subquery rows are equal
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
or unequal, respectively (including the special
case where the subquery returns no rows).
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result is <quote>false</> if any row is found to be unequal or equal,
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
respectively.
</para>
<para>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
As usual, null values in the expressions or subquery rows are combined per
Spell-check and markup police
2002-01-20 23:19:57 +01:00
the normal rules of SQL Boolean expressions. Two rows are considered
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
equal if all their corresponding members are non-null and equal; the rows
are unequal if any corresponding members are non-null and unequal;
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
otherwise the result of that row comparison is unknown (null).
If there is at least one null row result, then the result of <token>ALL</token>
cannot be true; it will be false or null.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</sect2>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
<sect2>
<title>Row-wise Comparison</title>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
<synopsis>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
(<replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ...</optional>) <replaceable>operator</replaceable> (<replaceable>subquery</replaceable>)
(<replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ...</optional>) <replaceable>operator</replaceable> (<replaceable>expression</replaceable> <optional>, <replaceable>expression</replaceable> ...</optional>)
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
</synopsis>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
<para>
The left-hand side is a list of scalar expressions. The right-hand side
can be either a list of scalar expressions of the same length, or a
parenthesized subquery, which must return exactly as many columns as there
are expressions on the left-hand side. Furthermore, the subquery cannot
return more than one row. (If it returns zero rows, the result is taken to
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
be null.) The left-hand side is evaluated and compared row-wise to the
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
single subquery result row, or to the right-hand expression list.
Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. Implement SQL99 SIMILAR TO as a synonym for our existing operator "~". Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape). Extend the definition to make the FOR clause optional. Define textregexsubstr() to actually implement this feature. Update the regression test to include these new string features. All tests pass. Rename the regular expression support routines from "pg95_xxx" to "pg_xxx". Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
2002-06-11 17:32:33 +02:00
Presently, only <literal>=</literal> and <literal>&lt;&gt;</literal> operators are allowed
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
in row-wise comparisons.
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
The result is <quote>true</> if the two rows are equal or unequal, respectively.
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
<para>
Add more appropriate markup.
2002-09-21 20:32:54 +02:00
As usual, null values in the expressions or subquery rows are combined per
Spell-check and markup police
2002-01-20 23:19:57 +01:00
the normal rules of SQL Boolean expressions. Two rows are considered
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
equal if all their corresponding members are non-null and equal; the rows
are unequal if any corresponding members are non-null and unequal;
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
otherwise the result of the row comparison is unknown (null).
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</para>
Merge documentation updates from 7.3 branch.
2002-11-11 21:14:04 +01:00
</sect2>
Provide some documentation for EXISTS, IN, NOT IN, ANY/SOME/ALL, and row comparisons. How'd this manage to slip through the cracks?
2001-12-01 05:19:20 +01:00
</sect1>
Merge functions and operators chapters. Lots of updates.
2000-12-14 23:30:56 +01:00
</chapter>
Split function and operator User Guide info from datatype.sgml into separate files. Add type conversion information. Format historical release notes.
1998-07-08 15:53:15 +02:00
Augment info on string functions per Jose Soares' suggestions.
1999-01-19 17:11:18 +01:00
<!-- Keep this comment at the end of the file
Local variables:
Accumulated fixups. Add some chapters on new topics. Change to referencing OASIS/Docbook v3.1 rather than Davenport/Docbook v3.0 Grepped for and fixed apparent tag mangling from emacs "Normalize" operation. Should be the last of those.
2000-03-31 00:22:41 +02:00
mode:sgml
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
sgml-omittag:nil
Augment info on string functions per Jose Soares' suggestions.
1999-01-19 17:11:18 +01:00
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:"./reference.ced"
sgml-exposed-tags:nil
Accumulated fixups. Add some chapters on new topics. Change to referencing OASIS/Docbook v3.1 rather than Davenport/Docbook v3.0 Grepped for and fixed apparent tag mangling from emacs "Normalize" operation. Should be the last of those.
2000-03-31 00:22:41 +02:00
sgml-local-catalogs:("/usr/lib/sgml/catalog")
Augment info on string functions per Jose Soares' suggestions.
1999-01-19 17:11:18 +01:00
sgml-local-ecat-files:nil
End:
-->