mirror of
https://github.com/postgres/postgres.git
synced 2025-07-28 23:42:10 +03: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.
This commit is contained in:
Thomas G. Lockhart
@ -1,13 +1,16 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/admin.sgml,v 1.11 1999/05/04 02:16:57 thomas Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/admin.sgml,v 1.12 1999/05/12 07:32:42 thomas Exp $
|
||||
|
||||
Postgres Administrator's Guide.
|
||||
Derived from postgres.sgml.
|
||||
- thomas 1998-10-27
|
||||
|
||||
$Log: admin.sgml,v $
|
||||
Revision 1.11 1999/05/04 02:16:57 thomas
|
||||
Include chapter on security.
|
||||
Revision 1.12 1999/05/12 07:32:42 thomas
|
||||
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.
|
||||
|
||||
Revision 1.10 1999/01/19 16:06:25 thomas
|
||||
Merge current.sgml into release.sgml so all release notes are in the same
|
||||
@ -59,8 +62,8 @@ Bigger updates to the installation instructions (install and config).
|
||||
|
||||
<!-- Title information -->
|
||||
|
||||
<Title>PostgreSQL Administrator's Guide</Title>
|
||||
<BookInfo>
|
||||
<Title>PostgreSQL Administrator's Guide</Title>
|
||||
<BookInfo>
|
||||
<ReleaseInfo>Covering v6.4 for general release</ReleaseInfo>
|
||||
<BookBiblio>
|
||||
<AuthorGroup>
|
||||
@ -84,17 +87,17 @@ Bigger updates to the installation instructions (install and config).
|
||||
<AuthorInitials>TGL</AuthorInitials>
|
||||
-->
|
||||
|
||||
<Date>(last updated 1998-10-27)</Date>
|
||||
<Date>(last updated 1999-04-08)</Date>
|
||||
</BookBiblio>
|
||||
|
||||
<LegalNotice>
|
||||
<Para>
|
||||
<ProductName>PostgreSQL</ProductName> is copyright (C) 1998
|
||||
by the Postgres Global Development Group.
|
||||
</Para>
|
||||
</LegalNotice>
|
||||
<LegalNotice>
|
||||
<Para>
|
||||
<ProductName>PostgreSQL</ProductName> is copyright (C) 1998-9
|
||||
by the Postgres Global Development Group.
|
||||
</Para>
|
||||
</LegalNotice>
|
||||
|
||||
</BookInfo>
|
||||
</BookInfo>
|
||||
|
||||
<!--
|
||||
<TOC> </TOC>
|
||||
@ -109,36 +112,36 @@ Your name here...
|
||||
</Dedication>
|
||||
-->
|
||||
|
||||
<Preface id="preface">
|
||||
<Title>Summary</Title>
|
||||
<Preface id="preface">
|
||||
<Title>Summary</Title>
|
||||
|
||||
<Para>
|
||||
<ProductName>Postgres</ProductName>,
|
||||
<Para>
|
||||
<ProductName>Postgres</ProductName>,
|
||||
developed originally in the UC Berkeley Computer Science Department,
|
||||
pioneered many of the object-relational concepts
|
||||
now becoming available in some commercial databases.
|
||||
It provides SQL92/SQL3 language support,
|
||||
It provides SQL92/SQL3 language support,
|
||||
transaction integrity, and type extensibility.
|
||||
<ProductName>PostgreSQL</ProductName> is a public-domain, open source descendant
|
||||
of this original Berkeley code.
|
||||
</Para>
|
||||
</Preface>
|
||||
</Para>
|
||||
</Preface>
|
||||
|
||||
&intro-ag;
|
||||
&intro-ag;
|
||||
|
||||
&ports;
|
||||
&config;
|
||||
&install;
|
||||
&installw;
|
||||
&runtime;
|
||||
&security;
|
||||
&options;
|
||||
&start-ag;
|
||||
&recovery;
|
||||
®ress;
|
||||
&release;
|
||||
&ports;
|
||||
&config;
|
||||
&install;
|
||||
&installw;
|
||||
&runtime;
|
||||
&security;
|
||||
&options;
|
||||
&start-ag;
|
||||
&recovery;
|
||||
®ress;
|
||||
&release;
|
||||
|
||||
&biblio;
|
||||
&biblio;
|
||||
|
||||
<!--
|
||||
Don't bother with an index until we get some index entries.
|
||||
|
||||
@ -2,7 +2,8 @@
|
||||
<title>Bibliography</title>
|
||||
|
||||
<para>
|
||||
Selected references and readings for <acronym>SQL</acronym> and <productname>Postgres</productname>.
|
||||
Selected references and readings for <acronym>SQL</acronym>
|
||||
and <productname>Postgres</productname>.
|
||||
</para>
|
||||
|
||||
<bibliodiv>
|
||||
|
||||
@ -1,49 +1,49 @@
|
||||
<chapter id="datatype">
|
||||
<title>Data Types</title>
|
||||
<chapter id="datatype">
|
||||
<title>Data Types</title>
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
Describes the built-in data types available in
|
||||
<productname>Postgres</productname>.
|
||||
</para>
|
||||
</abstract>
|
||||
<abstract>
|
||||
<para>
|
||||
Describes the built-in data types available in
|
||||
<productname>Postgres</productname>.
|
||||
</para>
|
||||
</abstract>
|
||||
|
||||
<para>
|
||||
<productname>Postgres</productname> has a rich set of native data
|
||||
types available to users.
|
||||
Users may add new types to <productname>Postgres</productname> using the
|
||||
<command>DEFINE TYPE</command>
|
||||
command described elsewhere.
|
||||
</para>
|
||||
<para>
|
||||
<productname>Postgres</productname> has a rich set of native data
|
||||
types available to users.
|
||||
Users may add new types to <productname>Postgres</productname> using the
|
||||
<command>DEFINE TYPE</command>
|
||||
command described elsewhere.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In the context of data types, the following sections will discuss
|
||||
<acronym>SQL</acronym> standards compliance, porting issues, and usage.
|
||||
<para>
|
||||
In the context of data types, the following sections will discuss
|
||||
<acronym>SQL</acronym> standards compliance, porting issues, and usage.
|
||||
|
||||
Some <productname>Postgres</productname> types correspond directly to
|
||||
<acronym>SQL92</acronym>-compatible types. In other
|
||||
cases, data types defined by <acronym>SQL92</acronym> syntax are mapped directly
|
||||
into native <productname>Postgres</productname> types.
|
||||
Some <productname>Postgres</productname> types correspond directly to
|
||||
<acronym>SQL92</acronym>-compatible types. In other
|
||||
cases, data types defined by <acronym>SQL92</acronym> syntax are mapped directly
|
||||
into native <productname>Postgres</productname> types.
|
||||
|
||||
Many of the built-in types have obvious external formats. However, several
|
||||
types are either unique to <productname>Postgres</productname>,
|
||||
such as open and closed paths, or have
|
||||
several possibilities for formats, such as the date and time types.
|
||||
</para>
|
||||
Many of the built-in types have obvious external formats. However, several
|
||||
types are either unique to <productname>Postgres</productname>,
|
||||
such as open and closed paths, or have
|
||||
several possibilities for formats, such as the date and time types.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<table tocentry="1">
|
||||
<title><productname>Postgres</productname> Data Types</title>
|
||||
<titleabbrev>Data Types</titleabbrev>
|
||||
<tgroup cols="3">
|
||||
<thead>
|
||||
<para>
|
||||
<table tocentry="1">
|
||||
<title><productname>Postgres</productname> Data Types</title>
|
||||
<titleabbrev>Data Types</titleabbrev>
|
||||
<tgroup cols="3">
|
||||
<thead>
|
||||
<row>
|
||||
<entry><productname>Postgres</productname> Type</entry>
|
||||
<entry><acronym>SQL92</acronym> or <acronym>SQL3</acronym> Type</entry>
|
||||
<entry>Description</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>bool</entry>
|
||||
<entry>boolean</entry>
|
||||
@ -169,32 +169,32 @@ several possibilities for formats, such as the date and time types.
|
||||
<entry>character varying(n)</entry>
|
||||
<entry>variable-length character string</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
</para>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<note>
|
||||
<para>
|
||||
The <type>cidr</type> and <type>inet</type> types are designed to handle any IP type
|
||||
but only ipv4 is handled in the current implementation.
|
||||
Everything here that talks about ipv4 will apply to ipv6 in a future release.</para>
|
||||
</note></para>
|
||||
<para>
|
||||
<note>
|
||||
<para>
|
||||
The <type>cidr</type> and <type>inet</type> types are designed to handle any IP type
|
||||
but only ipv4 is handled in the current implementation.
|
||||
Everything here that talks about ipv4 will apply to ipv6 in a future release.</para>
|
||||
</note></para>
|
||||
|
||||
<para>
|
||||
<table tocentry="1">
|
||||
<title><productname>Postgres</productname> Function Constants</title>
|
||||
<titleabbrev>Constants</titleabbrev>
|
||||
<tgroup cols="3">
|
||||
<thead>
|
||||
<para>
|
||||
<table tocentry="1">
|
||||
<title><productname>Postgres</productname> Function Constants</title>
|
||||
<titleabbrev>Constants</titleabbrev>
|
||||
<tgroup cols="3">
|
||||
<thead>
|
||||
<row>
|
||||
<entry><productname>Postgres</productname> Function</entry>
|
||||
<entry><acronym>SQL92</acronym> Constant</entry>
|
||||
<entry>Description</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>getpgusername()</entry>
|
||||
<entry>current_user</entry>
|
||||
@ -215,57 +215,57 @@ Everything here that talks about ipv4 will apply to ipv6 in a future release.</p
|
||||
<entry>current_timestamp</entry>
|
||||
<entry>date and time of current transaction</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
</para>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<productname>Postgres</productname> has features at the forefront of
|
||||
<acronym>ORDBMS</acronym> development. In addition to
|
||||
<acronym>SQL3</acronym> conformance, substantial portions
|
||||
of <acronym>SQL92</acronym> are also supported.
|
||||
Although we strive for <acronym>SQL92</acronym> compliance,
|
||||
there are some aspects of the standard
|
||||
which are ill considered and which should not live through subsequent standards.
|
||||
<productname>Postgres</productname> will not make great efforts to
|
||||
conform to these features; however, these tend to apply in little-used
|
||||
or obsure cases, and a typical user is not likely to run into them.</para>
|
||||
<para>
|
||||
<productname>Postgres</productname> has features at the forefront of
|
||||
<acronym>ORDBMS</acronym> development. In addition to
|
||||
<acronym>SQL3</acronym> conformance, substantial portions
|
||||
of <acronym>SQL92</acronym> are also supported.
|
||||
Although we strive for <acronym>SQL92</acronym> compliance,
|
||||
there are some aspects of the standard
|
||||
which are ill considered and which should not live through subsequent standards.
|
||||
<productname>Postgres</productname> will not make great efforts to
|
||||
conform to these features; however, these tend to apply in little-used
|
||||
or obsure cases, and a typical user is not likely to run into them.</para>
|
||||
|
||||
<para>
|
||||
Most of the input and output functions corresponding to the
|
||||
base types (e.g., integers and floating point numbers) do some
|
||||
error-checking.
|
||||
Some of the operators and functions (e.g.,
|
||||
addition and multiplication) do not perform run-time error-checking in the
|
||||
interests of improving execution speed.
|
||||
On some systems, for example, the numeric operators for some data types may
|
||||
silently underflow or overflow.
|
||||
</para>
|
||||
<para>
|
||||
Most of the input and output functions corresponding to the
|
||||
base types (e.g., integers and floating point numbers) do some
|
||||
error-checking.
|
||||
Some of the operators and functions (e.g.,
|
||||
addition and multiplication) do not perform run-time error-checking in the
|
||||
interests of improving execution speed.
|
||||
On some systems, for example, the numeric operators for some data types may
|
||||
silently underflow or overflow.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Note that some of the input and output functions are not invertible. That is,
|
||||
the result of an output function may lose precision when compared to
|
||||
the original input.
|
||||
<para>
|
||||
Note that some of the input and output functions are not invertible. That is,
|
||||
the result of an output function may lose precision when compared to
|
||||
the original input.
|
||||
|
||||
<note>
|
||||
<para>
|
||||
The original <productname>Postgres</productname> v4.2 code received from
|
||||
Berkeley rounded all double precision floating point results to six digits for
|
||||
output. Starting with v6.1, floating point numbers are allowed to retain
|
||||
most of the intrinsic precision of the type (typically 15 digits for doubles,
|
||||
6 digits for 4-byte floats).
|
||||
Other types with underlying floating point fields (e.g. geometric
|
||||
types) carry similar precision.</para>
|
||||
</note>
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
The original <productname>Postgres</productname> v4.2 code received from
|
||||
Berkeley rounded all double precision floating point results to six digits for
|
||||
output. Starting with v6.1, floating point numbers are allowed to retain
|
||||
most of the intrinsic precision of the type (typically 15 digits for doubles,
|
||||
6 digits for 4-byte floats).
|
||||
Other types with underlying floating point fields (e.g. geometric
|
||||
types) carry similar precision.</para>
|
||||
</note>
|
||||
</para>
|
||||
|
||||
<sect1>
|
||||
<title>Numeric Types</title>
|
||||
<sect1>
|
||||
<title>Numeric Types</title>
|
||||
|
||||
<para>
|
||||
Numeric types consist of two- and four-byte integers and four- and eight-byte
|
||||
floating point numbers.</para>
|
||||
<para>
|
||||
Numeric types consist of two- and four-byte integers and four- and eight-byte
|
||||
floating point numbers.</para>
|
||||
|
||||
<para>
|
||||
<table tocentry="1">
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,26 +1,26 @@
|
||||
<Chapter Id="operators">
|
||||
<Title>Operators</Title>
|
||||
<Chapter Id="operators">
|
||||
<Title id="operators-title">Operators</Title>
|
||||
|
||||
<Abstract>
|
||||
<Para>
|
||||
Describes the built-in operators available in
|
||||
<ProductName>Postgres</ProductName>.
|
||||
</Para>
|
||||
</Abstract>
|
||||
<Abstract>
|
||||
<Para>
|
||||
Describes the built-in operators available in
|
||||
<ProductName>Postgres</ProductName>.
|
||||
</Para>
|
||||
</Abstract>
|
||||
|
||||
<Para>
|
||||
<ProductName>Postgres</ProductName> provides a large number of
|
||||
built-in operators on system types.
|
||||
These operators are declared in the system catalog
|
||||
pg_operator. Every entry in pg_operator includes
|
||||
the name of the procedure that implements the operator and the
|
||||
class <Acronym>OIDs</Acronym> of the input and output types.
|
||||
</Para>
|
||||
<Para>
|
||||
<ProductName>Postgres</ProductName> provides a large number of
|
||||
built-in operators on system types.
|
||||
These operators are declared in the system catalog
|
||||
pg_operator. Every entry in pg_operator includes
|
||||
the name of the procedure that implements the operator and the
|
||||
class <Acronym>OIDs</Acronym> of the input and output types.
|
||||
</Para>
|
||||
|
||||
<Para>
|
||||
To view all variations of the <Quote>||</Quote> string concatenation operator,
|
||||
try
|
||||
<ProgramListing>
|
||||
<Para>
|
||||
To view all variations of the <Quote>||</Quote> string concatenation operator,
|
||||
try
|
||||
<ProgramListing>
|
||||
SELECT oprleft, oprright, oprresult, oprcode
|
||||
FROM pg_operator WHERE oprname = '||';
|
||||
|
||||
@ -30,37 +30,37 @@ oprleft|oprright|oprresult|oprcode
|
||||
1042| 1042| 1042|textcat
|
||||
1043| 1043| 1043|textcat
|
||||
(3 rows)
|
||||
</ProgramListing>
|
||||
</Para>
|
||||
</ProgramListing>
|
||||
</Para>
|
||||
|
||||
<Para>
|
||||
Users may invoke operators using the operator name, as in:
|
||||
<Para>
|
||||
Users may invoke operators using the operator name, as in:
|
||||
|
||||
<ProgramListing>
|
||||
<ProgramListing>
|
||||
select * from emp where salary < 40000;
|
||||
</ProgramListing>
|
||||
</ProgramListing>
|
||||
|
||||
Alternatively, users may call the functions that implement the
|
||||
operators directly. In this case, the query above would be expressed
|
||||
as:
|
||||
<ProgramListing>
|
||||
Alternatively, users may call the functions that implement the
|
||||
operators directly. In this case, the query above would be expressed
|
||||
as:
|
||||
<ProgramListing>
|
||||
select * from emp where int4lt(salary, 40000);
|
||||
</ProgramListing>
|
||||
</Para>
|
||||
</ProgramListing>
|
||||
</Para>
|
||||
|
||||
<Para>
|
||||
<Application>psql</Application>
|
||||
has a command (<Command>\dd</Command>) to show these operators.
|
||||
</Para>
|
||||
<Para>
|
||||
<Application>psql</Application>
|
||||
has a command (<Command>\dd</Command>) to show these operators.
|
||||
</Para>
|
||||
|
||||
<sect1>
|
||||
<title>Lexical Precedence</title>
|
||||
<sect1>
|
||||
<title>Lexical Precedence</title>
|
||||
|
||||
<para>
|
||||
Operators have a precedence which is currently hardcoded into the parser.
|
||||
Most operators have the same precedence and are left-associative. This may lead
|
||||
to non-intuitive behavior; for example the boolean operators "<" and ">"
|
||||
have a different precedence that the boolean operators "<=" and ">=".
|
||||
<para>
|
||||
Operators have a precedence which is currently hardcoded into the parser.
|
||||
Most operators have the same precedence and are left-associative. This may lead
|
||||
to non-intuitive behavior; for example the boolean operators "<" and ">"
|
||||
have a different precedence that the boolean operators "<=" and ">=".
|
||||
|
||||
<table tocentry="1">
|
||||
<title>
|
||||
@ -322,26 +322,27 @@ logical union
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1>
|
||||
<title>General Operators</title>
|
||||
<sect1>
|
||||
<title>General Operators</title>
|
||||
|
||||
<para>
|
||||
The operators listed here are defined for a number of native data types,
|
||||
ranging from numeric types to data/time types.
|
||||
</para>
|
||||
<Para>
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName> Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<para>
|
||||
The operators listed here are defined for a number of native data types,
|
||||
ranging from numeric types to data/time types.
|
||||
</para>
|
||||
|
||||
<Para>
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName> Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<ROW>
|
||||
<ENTRY>Operator</ENTRY>
|
||||
<ENTRY>Description</ENTRY>
|
||||
<ENTRY>Usage</ENTRY>
|
||||
</ROW>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
<ROW>
|
||||
<ENTRY> < </ENTRY>
|
||||
<ENTRY>Less than?</ENTRY>
|
||||
@ -412,28 +413,28 @@ ranging from numeric types to data/time types.
|
||||
<ENTRY>Does not match (regex), case insensitive</ENTRY>
|
||||
<ENTRY>'thomas' !~ '.*vadim.*'</ENTRY>
|
||||
</ROW>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</sect1>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</sect1>
|
||||
|
||||
<sect1>
|
||||
<title id="math-opers">Numerical Operators</title>
|
||||
<sect1>
|
||||
<title id="math-opers">Numerical Operators</title>
|
||||
|
||||
<Para>
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName> Numerical Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<Para>
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName> Numerical Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<ROW>
|
||||
<ENTRY>Operator</ENTRY>
|
||||
<ENTRY>Description</ENTRY>
|
||||
<ENTRY>Usage</ENTRY>
|
||||
</ROW>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
<ROW>
|
||||
<ENTRY> ! </ENTRY>
|
||||
<ENTRY>Factorial</ENTRY>
|
||||
@ -504,28 +505,28 @@ ranging from numeric types to data/time types.
|
||||
<ENTRY>Cube root</ENTRY>
|
||||
<ENTRY>||/ 27.0</ENTRY>
|
||||
</ROW>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</sect1>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</sect1>
|
||||
|
||||
<sect1>
|
||||
<title>Geometric Operators</title>
|
||||
<sect1>
|
||||
<title>Geometric Operators</title>
|
||||
|
||||
<Para>
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName> Geometric Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<Para>
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName> Geometric Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<ROW>
|
||||
<ENTRY>Operator</ENTRY>
|
||||
<ENTRY>Description</ENTRY>
|
||||
<ENTRY>Usage</ENTRY>
|
||||
</ROW>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
<ROW>
|
||||
<ENTRY> + </ENTRY>
|
||||
<ENTRY>Translation</ENTRY>
|
||||
@ -646,32 +647,32 @@ ranging from numeric types to data/time types.
|
||||
<ENTRY>Same as</ENTRY>
|
||||
<ENTRY>'((0,0),(1,1))'::polygon ~= '((1,1),(0,0))'::polygon</ENTRY>
|
||||
</ROW>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</sect1>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</sect1>
|
||||
|
||||
<sect1>
|
||||
<title>Time Interval Operators</title>
|
||||
<sect1>
|
||||
<title>Time Interval Operators</title>
|
||||
|
||||
<Para>
|
||||
The time interval data type <Type>tinterval</Type> is a legacy from the original
|
||||
date/time types and is not as well supported as the more modern types. There
|
||||
are several operators for this type.
|
||||
<Para>
|
||||
The time interval data type <Type>tinterval</Type> is a legacy from the original
|
||||
date/time types and is not as well supported as the more modern types. There
|
||||
are several operators for this type.
|
||||
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName> Time Interval Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName> Time Interval Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<ROW>
|
||||
<ENTRY>Operator</ENTRY>
|
||||
<ENTRY>Description</ENTRY>
|
||||
<ENTRY>Usage</ENTRY>
|
||||
</ROW>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
<ROW>
|
||||
<ENTRY> #< </ENTRY>
|
||||
<ENTRY>Interval less than?</ENTRY>
|
||||
@ -727,28 +728,28 @@ are several operators for this type.
|
||||
<ENTRY>Time inside interval?</ENTRY>
|
||||
<ENTRY></ENTRY>
|
||||
</ROW>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</sect1>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</sect1>
|
||||
|
||||
<Sect1>
|
||||
<title id="cidr-opers">IP V4 CIDR Operators</title>
|
||||
<Sect1>
|
||||
<title id="cidr-opers">IP V4 CIDR Operators</title>
|
||||
|
||||
<Para>
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName>IP V4 CIDR Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<Para>
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName>IP V4 CIDR Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<ROW>
|
||||
<ENTRY>Operator</ENTRY>
|
||||
<ENTRY>Description</ENTRY>
|
||||
<ENTRY>Usage</ENTRY>
|
||||
</ROW>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
<ROW>
|
||||
<ENTRY> < </ENTRY>
|
||||
<ENTRY>Less than</ENTRY>
|
||||
@ -799,28 +800,28 @@ are several operators for this type.
|
||||
<ENTRY>contains or equals</ENTRY>
|
||||
<ENTRY>'192.168.1/24'::cidr >>= '192.168.1/24'::cidr</ENTRY>
|
||||
</ROW>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</Sect1>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</Sect1>
|
||||
|
||||
<Sect1>
|
||||
<title id="inet-opers">IP V4 INET Operators</title>
|
||||
<Sect1>
|
||||
<title id="inet-opers">IP V4 INET Operators</title>
|
||||
|
||||
<Para>
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName>IP V4 INET Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<Para>
|
||||
<TABLE TOCENTRY="1">
|
||||
<TITLE><ProductName>Postgres</ProductName>IP V4 INET Operators</TITLE>
|
||||
<TITLEABBREV>Operators</TITLEABBREV>
|
||||
<TGROUP COLS="3">
|
||||
<THEAD>
|
||||
<ROW>
|
||||
<ENTRY>Operator</ENTRY>
|
||||
<ENTRY>Description</ENTRY>
|
||||
<ENTRY>Usage</ENTRY>
|
||||
</ROW>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
</THEAD>
|
||||
<TBODY>
|
||||
<ROW>
|
||||
<ENTRY> < </ENTRY>
|
||||
<ENTRY>Less than</ENTRY>
|
||||
@ -871,11 +872,27 @@ are several operators for this type.
|
||||
<ENTRY>contains or equals</ENTRY>
|
||||
<ENTRY>'192.168.1/24'::inet >>= '192.168.1/24'::inet</ENTRY>
|
||||
</ROW>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</Sect1>
|
||||
</TBODY>
|
||||
</TGROUP>
|
||||
</TABLE>
|
||||
</Para>
|
||||
</Sect1>
|
||||
|
||||
</Chapter>
|
||||
</Chapter>
|
||||
|
||||
<!-- Keep this comment at the end of the file
|
||||
Local variables:
|
||||
mode: sgml
|
||||
sgml-omittag:nil
|
||||
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
|
||||
sgml-local-catalogs:"/usr/lib/sgml/CATALOG"
|
||||
sgml-local-ecat-files:nil
|
||||
End:
|
||||
-->
|
||||
|
||||
@ -1,62 +1,73 @@
|
||||
<chapter>
|
||||
<title>SQL Syntax</title>
|
||||
<chapter>
|
||||
<title>SQL Syntax</title>
|
||||
|
||||
<sect1>
|
||||
<title>Key Words</title>
|
||||
<abstract>
|
||||
<para>
|
||||
<acronym>SQL</acronym> manipulates sets of data. The language is
|
||||
composed of various <firstterm>key words</firstterm>. Arithmetic
|
||||
and procedural expressions are allowed. We will cover these topics
|
||||
in this chapter; subsequent chapters will include details on data
|
||||
types, functions, and operators.
|
||||
</para>
|
||||
</abstract>
|
||||
|
||||
<para>
|
||||
<acronym>SQL92</acronym> defines <firstterm>key words</firstterm>
|
||||
for the language
|
||||
which have specific meaning. Some key words are
|
||||
<firstterm>reserved</firstterm>, which indicates that they are
|
||||
restricted to appear in only certain contexts. Other key words are
|
||||
<firstterm>not restricted</firstterm>, which indicates that in certain
|
||||
contexts they
|
||||
have a specific meaning but are not otherwise constrained.
|
||||
</para>
|
||||
<sect1>
|
||||
<title>Key Words</title>
|
||||
|
||||
<para>
|
||||
<productname>Postgres</productname> implements an extended subset of the
|
||||
<acronym>SQL92</acronym> and <acronym>SQL3</acronym> languages. Some language
|
||||
elements are not as restricted in this implementation as is
|
||||
called for in the language standards, in part due
|
||||
to the extensibility features of <productname>Postgres</productname>.
|
||||
</para>
|
||||
<para>
|
||||
<acronym>SQL92</acronym> defines <firstterm>key words</firstterm>
|
||||
for the language
|
||||
which have specific meaning. Some key words are
|
||||
<firstterm>reserved</firstterm>, which indicates that they are
|
||||
restricted to appear in only certain contexts. Other key words are
|
||||
<firstterm>not restricted</firstterm>, which indicates that in certain
|
||||
contexts they
|
||||
have a specific meaning but are not otherwise constrained.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Information on <acronym>SQL92</acronym> and <acronym>SQL3</acronym> key words
|
||||
is derived from <xref linkend="DATE97" endterm="DATE97">.
|
||||
</para>
|
||||
<para>
|
||||
<productname>Postgres</productname> implements an extended subset of the
|
||||
<acronym>SQL92</acronym> and <acronym>SQL3</acronym> languages. Some language
|
||||
elements are not as restricted in this implementation as is
|
||||
called for in the language standards, in part due
|
||||
to the extensibility features of <productname>Postgres</productname>.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Reserved Key Words</title>
|
||||
<para>
|
||||
Information on <acronym>SQL92</acronym> and <acronym>SQL3</acronym> key words
|
||||
is derived from <xref linkend="DATE97" endterm="DATE97">.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<acronym>SQL92</acronym> and <acronym>SQL3</acronym> have
|
||||
<firstterm>reserved key words</firstterm> which are not allowed
|
||||
as identifiers and not allowed in any usage other than as fundamental
|
||||
tokens in <acronym>SQL</acronym> statements.
|
||||
<productname>Postgres</productname> has additional key words
|
||||
which have similar restrictions. In particular, these key words
|
||||
are not allowed as column or table names, though in some cases
|
||||
they are allowed to be column labels (i.e. in AS clauses).
|
||||
</para>
|
||||
<sect2>
|
||||
<title>Reserved Key Words</title>
|
||||
|
||||
<tip>
|
||||
<para>
|
||||
Any string can be specified as an identifier if surrounded by
|
||||
double quotes (<quote>like this!</quote>). Some care is required since
|
||||
such an identifier will be case sensitive
|
||||
and will retain embedded whitespace other special characters.</para>
|
||||
</tip>
|
||||
<para>
|
||||
<acronym>SQL92</acronym> and <acronym>SQL3</acronym> have
|
||||
<firstterm>reserved key words</firstterm> which are not allowed
|
||||
as identifiers and not allowed in any usage other than as fundamental
|
||||
tokens in <acronym>SQL</acronym> statements.
|
||||
<productname>Postgres</productname> has additional key words
|
||||
which have similar restrictions. In particular, these key words
|
||||
are not allowed as column or table names, though in some cases
|
||||
they are allowed to be column labels (i.e. in AS clauses).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The following are <productname>Postgres</productname>
|
||||
reserved words which are neither <acronym>SQL92</acronym>
|
||||
nor <acronym>SQL3</acronym> reserved words. These are allowed
|
||||
to be present as column labels, but not as identifiers:
|
||||
<tip>
|
||||
<para>
|
||||
Any string can be specified as an identifier if surrounded by
|
||||
double quotes (<quote>like this!</quote>). Some care is required since
|
||||
such an identifier will be case sensitive
|
||||
and will retain embedded whitespace other special characters.
|
||||
</para>
|
||||
</tip>
|
||||
|
||||
<programlisting>
|
||||
<para>
|
||||
The following are <productname>Postgres</productname>
|
||||
reserved words which are neither <acronym>SQL92</acronym>
|
||||
nor <acronym>SQL3</acronym> reserved words. These are allowed
|
||||
to be present as column labels, but not as identifiers:
|
||||
|
||||
<programlisting>
|
||||
ABORT ANALYZE
|
||||
BINARY
|
||||
CLUSTER CONSTRAINT COPY
|
||||
@ -69,32 +80,33 @@ RESET
|
||||
SETOF SHOW
|
||||
UNLISTEN UNTIL
|
||||
VACUUM VERBOSE
|
||||
</programlisting>
|
||||
</para>
|
||||
</programlisting>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The following are <productname>Postgres</productname>
|
||||
reserved words which are also <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> reserved words, and which
|
||||
are allowed to be present as column labels, but not as identifiers:
|
||||
<para>
|
||||
The following are <productname>Postgres</productname>
|
||||
reserved words which are also <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> reserved words, and which
|
||||
are allowed to be present as column labels, but not as identifiers:
|
||||
|
||||
<programlisting>
|
||||
<programlisting>
|
||||
CASE COALESCE CROSS CURRENT
|
||||
ELSE END
|
||||
FALSE FOREIGN
|
||||
GROUP
|
||||
GLOBAL GROUP
|
||||
LOCAL
|
||||
NULLIF
|
||||
ORDER
|
||||
POSITION PRECISION
|
||||
TABLE THEN TRANSACTION TRUE
|
||||
WHEN
|
||||
</programlisting>
|
||||
</programlisting>
|
||||
|
||||
The following are <productname>Postgres</productname>
|
||||
reserved words which are also <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> reserved words:
|
||||
The following are <productname>Postgres</productname>
|
||||
reserved words which are also <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> reserved words:
|
||||
|
||||
<programlisting>
|
||||
<programlisting>
|
||||
ADD ALL ALTER AND ANY AS ASC
|
||||
BEGIN BETWEEN BOTH BY
|
||||
CASCADE CAST CHAR CHARACTER CHECK CLOSE
|
||||
@ -118,49 +130,49 @@ TO TRAILING TRIM
|
||||
UNION UNIQUE UPDATE USER USING
|
||||
VALUES VARCHAR VARYING VIEW
|
||||
WHERE WITH WORK
|
||||
</programlisting>
|
||||
</para>
|
||||
</programlisting>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The following are <acronym>SQL92</acronym> reserved key words which
|
||||
are not <productname>Postgres</productname> reserved key words, but which
|
||||
if used as function names are always translated into the function
|
||||
<function>length</function>:
|
||||
<para>
|
||||
The following are <acronym>SQL92</acronym> reserved key words which
|
||||
are not <productname>Postgres</productname> reserved key words, but which
|
||||
if used as function names are always translated into the function
|
||||
<function>length</function>:
|
||||
|
||||
<programlisting>
|
||||
<programlisting>
|
||||
CHAR_LENGTH CHARACTER_LENGTH
|
||||
</programlisting>
|
||||
</para>
|
||||
</programlisting>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The following are <acronym>SQL92</acronym> or <acronym>SQL3</acronym>
|
||||
reserved key words which
|
||||
are not <productname>Postgres</productname> reserved key words, but
|
||||
if used as type names are always translated into an alternate, native type:
|
||||
<para>
|
||||
The following are <acronym>SQL92</acronym> or <acronym>SQL3</acronym>
|
||||
reserved key words which
|
||||
are not <productname>Postgres</productname> reserved key words, but
|
||||
if used as type names are always translated into an alternate, native type:
|
||||
|
||||
<programlisting>
|
||||
<programlisting>
|
||||
BOOLEAN DOUBLE FLOAT INT INTEGER INTERVAL REAL SMALLINT
|
||||
</programlisting>
|
||||
</para>
|
||||
</programlisting>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The following are either <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> reserved key words
|
||||
which are not key words in <productname>Postgres</productname>.
|
||||
These have no proscribed usage in <productname>Postgres</productname>
|
||||
at the time of writing (v6.4) but may become reserved key words in the
|
||||
future:
|
||||
<para>
|
||||
The following are either <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> reserved key words
|
||||
which are not key words in <productname>Postgres</productname>.
|
||||
These have no proscribed usage in <productname>Postgres</productname>
|
||||
at the time of writing (v6.5) but may become reserved key words in the
|
||||
future:
|
||||
|
||||
<note>
|
||||
<para>
|
||||
Some of these key words represent functions in <acronym>SQL92</acronym>.
|
||||
These functions are defined in <productname>Postgres</productname>,
|
||||
but the parser does not consider the names to be key words and they are allowed
|
||||
in other contexts.
|
||||
</para>
|
||||
</note>
|
||||
<note>
|
||||
<para>
|
||||
Some of these key words represent functions in <acronym>SQL92</acronym>.
|
||||
These functions are defined in <productname>Postgres</productname>,
|
||||
but the parser does not consider the names to be key words and they are allowed
|
||||
in other contexts.
|
||||
</para>
|
||||
</note>
|
||||
|
||||
<programlisting>
|
||||
<programlisting>
|
||||
ALLOCATE ARE ASSERTION AT AUTHORIZATION AVG
|
||||
BIT BIT_LENGTH
|
||||
CASCADED CATALOG COLLATION CONNECT CONNECTION
|
||||
@ -168,7 +180,7 @@ CASCADED CATALOG COLLATION CONNECT CONNECTION
|
||||
DATE DEALLOCATE DEC DESCRIBE DESCRIPTOR DIAGNOSTICS DISCONNECT DOMAIN
|
||||
END-EXEC ESCAPE EXCEPT EXCEPTION EXEC EXTERNAL
|
||||
FIRST FOUND
|
||||
GET GLOBAL GO GOTO
|
||||
GET GO GOTO
|
||||
IDENTITY IMMEDIATE INDICATOR INITIALLY INPUT INTERSECT ISOLATION
|
||||
LAST LEVEL LOWER
|
||||
MAX MIN MODULE
|
||||
@ -181,56 +193,56 @@ TEMPORARY TRANSLATE TRANSLATION
|
||||
UNKNOWN UPPER USAGE
|
||||
VALUE
|
||||
WHENEVER WRITE
|
||||
</programlisting>
|
||||
</para>
|
||||
</sect2>
|
||||
</programlisting>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Non-reserved Keywords</title>
|
||||
<sect2>
|
||||
<title>Non-reserved Keywords</title>
|
||||
|
||||
<para>
|
||||
<acronym>SQL92</acronym> and <acronym>SQL3</acronym> have
|
||||
<firstterm>non-reserved keywords</firstterm> which have
|
||||
a proscribed meaning in the language but which are also allowed
|
||||
as identifiers.
|
||||
<productname>Postgres</productname> has additional keywords
|
||||
which allow similar unrestricted usage.
|
||||
In particular, these keywords
|
||||
are allowed as column or table names.
|
||||
</para>
|
||||
<para>
|
||||
<acronym>SQL92</acronym> and <acronym>SQL3</acronym> have
|
||||
<firstterm>non-reserved keywords</firstterm> which have
|
||||
a proscribed meaning in the language but which are also allowed
|
||||
as identifiers.
|
||||
<productname>Postgres</productname> has additional keywords
|
||||
which allow similar unrestricted usage.
|
||||
In particular, these keywords
|
||||
are allowed as column or table names.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The following are <productname>Postgres</productname>
|
||||
non-reserved key words which are neither <acronym>SQL92</acronym>
|
||||
nor <acronym>SQL3</acronym> non-reserved key words:
|
||||
<para>
|
||||
The following are <productname>Postgres</productname>
|
||||
non-reserved key words which are neither <acronym>SQL92</acronym>
|
||||
nor <acronym>SQL3</acronym> non-reserved key words:
|
||||
|
||||
<programlisting>
|
||||
AFTER AGGREGATE
|
||||
<programlisting>
|
||||
ACCESS AFTER AGGREGATE
|
||||
BACKWARD BEFORE
|
||||
CACHE CREATEDB CREATEUSER CYCLE
|
||||
DATABASE DELIMITERS
|
||||
EACH ENCODING
|
||||
EACH ENCODING EXCLUSIVE
|
||||
FORWARD FUNCTION
|
||||
HANDLER
|
||||
INCREMENT INDEX INHERITS INSENSITIVE INSTEAD ISNULL
|
||||
LANCOMPILER LOCATION
|
||||
MAXVALUE MINVALUE
|
||||
MAXVALUE MINVALUE MODE
|
||||
NOCREATEDB NOCREATEUSER NOTHING NOTNULL
|
||||
OIDS OPERATOR
|
||||
PASSWORD PROCEDURAL
|
||||
RECIPE RENAME RETURNS ROW RULE
|
||||
SEQUENCE SERIAL START STATEMENT STDIN STDOUT
|
||||
SEQUENCE SERIAL SHARE START STATEMENT STDIN STDOUT
|
||||
TRUSTED
|
||||
VALID VERSION
|
||||
</programlisting>
|
||||
</para>
|
||||
</programlisting>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The following are <productname>Postgres</productname>
|
||||
non-reserved key words which are <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> reserved key words:
|
||||
<para>
|
||||
The following are <productname>Postgres</productname>
|
||||
non-reserved key words which are <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> reserved key words:
|
||||
|
||||
<programlisting>
|
||||
<programlisting>
|
||||
ABSOLUTE ACTION
|
||||
DAY
|
||||
HOUR
|
||||
@ -246,30 +258,30 @@ SCROLL SECOND
|
||||
TIME TIMESTAMP TIMEZONE_HOUR TIMEZONE_MINUTE TRIGGER
|
||||
YEAR
|
||||
ZONE
|
||||
</programlisting>
|
||||
</para>
|
||||
</programlisting>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The following are <productname>Postgres</productname>
|
||||
non-reserved key words which are also either <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> non-reserved key words:
|
||||
<para>
|
||||
The following are <productname>Postgres</productname>
|
||||
non-reserved key words which are also either <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> non-reserved key words:
|
||||
|
||||
<programlisting>
|
||||
TYPE
|
||||
</programlisting>
|
||||
</para>
|
||||
<programlisting>
|
||||
COMMITTED SERIALIZABLE TYPE
|
||||
</programlisting>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The following are either <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> non-reserved key words which are not
|
||||
key words of any kind in <productname>Postgres</productname>:
|
||||
<para>
|
||||
The following are either <acronym>SQL92</acronym>
|
||||
or <acronym>SQL3</acronym> non-reserved key words which are not
|
||||
key words of any kind in <productname>Postgres</productname>:
|
||||
|
||||
<programlisting>
|
||||
<programlisting>
|
||||
ADA
|
||||
C CATALOG_NAME CHARACTER_SET_CATALOG CHARACTER_SET_NAME
|
||||
CHARACTER_SET_SCHEMA CLASS_ORIGIN COBOL COLLATION_CATALOG
|
||||
COLLATION_NAME COLLATION_SCHEMA COLUMN_NAME
|
||||
COMMAND_FUNCTION COMMITTED CONDITION_NUMBER
|
||||
COMMAND_FUNCTION CONDITION_NUMBER
|
||||
CONNECTION_NAME CONSTRAINT_CATALOG CONSTRAINT_NAME
|
||||
CONSTRAINT_SCHEMA CURSOR_NAME
|
||||
DATA DATE_TIME_INTERVAL_CODE DATE_TIME_INTERVAL_PRECISION
|
||||
@ -281,15 +293,29 @@ NAME NULLABLE NUMBER
|
||||
PAD PASCAL PLI
|
||||
REPEATABLE RETURNED_LENGTH RETURNED_OCTET_LENGTH
|
||||
RETURNED_SQLSTATE ROW_COUNT
|
||||
SCALE SCHEMA_NAME SERIALIZABLE SERVER_NAME SPACE
|
||||
SCALE SCHEMA_NAME SERVER_NAME SPACE
|
||||
SUBCLASS_ORIGIN
|
||||
TABLE_NAME
|
||||
UNCOMMITTED UNNAMED
|
||||
</programlisting>
|
||||
</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</chapter>
|
||||
</programlisting>
|
||||
</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1>
|
||||
<title>Expressions</title>
|
||||
|
||||
<para>
|
||||
<acronym>SQL92</acronym> allows <firstterm>expressions</firstterm>
|
||||
to transform data in expressions. Expressions may contain operators
|
||||
(see <xref linkend="operators-title" endterm="operators-title">
|
||||
for more details) and functions
|
||||
(<xref linkend="functions-title" endterm="functions-title"> has
|
||||
more information).
|
||||
|
||||
</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<!-- Keep this comment at the end of the file
|
||||
Local variables:
|
||||
|
||||
Reference in New Issue
Block a user