<A HREF="#4.12">4.12</A>) What is Genetic Query Optimization?<BR>
<A HREF="#4.13">4.13</A>) How do I do regular expression searches
-and case-insensitive regexp searching?<BR>
+and case-insensitive regular expression searching?<BR>
<A HREF="#4.14">4.14</A>) In a query, how do I detect if a field
is NULL?<BR>
<A HREF="#4.15">4.15</A>) What is the difference between the
in the distribution.
<P>
-There is a PostgreSQL book availiable at <A
+There is a PostgreSQL book available at <A
HREF="http://www.PostgreSQL.org/docs/awbook.html">
http://www.PostgreSQL.org/docs/awbook.html</A><P>
<H4><A NAME="4.13">4.13</A>) How do I do regular expression searches and
-case-insensitive regexp searching?</H4><P>
+case-insensitive regular expression searching?</H4><P>
The <I>~</I> operator does regular-expression matching, and <I>~*</I>
does case-insensitive regular-expression matching. There is no
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_user.sgml,v 1.12 2000/07/22 02:39:10 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_user.sgml,v 1.13 2000/07/22 04:30:26 momjian Exp $
Postgres documentation
-->
</programlisting>
Change a user's valid until date, specifying that his
- authorisation should expire at midday on 4th May 1998 using
+ authorization should expire at midday on 4th May 1998 using
the time zone which is one hour ahead of UTC:
<programlisting>
ALTER USER chris VALID UNTIL 'May 4 12:00:00 1998 +1';
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.8 2000/07/22 02:39:10 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.9 2000/07/22 04:30:26 momjian Exp $
Postgres documentation
-->
In other words, as the class is updated, the changes are
not clustered. No attempt is made to keep new instances or
updated tuples clustered. If one wishes, one can
- recluster manually by issuing the command again.
+ re-cluster manually by issuing the command again.
</para>
<refsect2 id="R2-SQL-CLUSTER-3">
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_constraint.sgml,v 1.1 2000/04/14 15:17:28 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_constraint.sgml,v 1.2 2000/07/22 04:30:27 momjian Exp $
Postgres documentation
-->
<term><replaceable class="PARAMETER">attributes</replaceable></term>
<listitem>
<para>
- Contraint attributes.
+ Constraint attributes.
</para>
</listitem>
</varlistentry>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_function.sgml,v 1.14 2000/07/22 02:39:10 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_function.sgml,v 1.15 2000/07/22 04:30:27 momjian Exp $
Postgres documentation
-->
LANGUAGE 'c';
</programlisting>
<para>
- The C decalaration of the function is:
+ The C declaration of the function is:
</para>
<programlisting>
Point * complex_to_point (Complex *z)
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.32 2000/07/22 02:39:10 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.33 2000/07/22 04:30:27 momjian Exp $
Postgres documentation
-->
Define a UNIQUE table constraint for the table distributors:
<programlisting>
CREATE TABLE distributors (
- did DECIMAL(03),
+ did DECIMAL(3),
name VARCHAR(40),
UNIQUE(name)
);
<programlisting>
CREATE TABLE distributors (
- did DECIMAL(03) PRIMARY KEY DEFAULT NEXTVAL('serial'),
+ did DECIMAL(3) PRIMARY KEY DEFAULT NEXTVAL('serial'),
name VARCHAR(40) NOT NULL CHECK (name <> '')
);
</programlisting>
CREATE TABLE films (
code CHAR(5),
title VARCHAR(40),
- did DECIMAL(03),
+ did DECIMAL(3),
date_prod DATE,
kind CHAR(10),
len INTERVAL HOUR TO MINUTE,
<programlisting>
CREATE TABLE films (
- code CHAR(05),
+ code CHAR(5),
title VARCHAR(40),
- did DECIMAL(03),
+ did DECIMAL(3),
date_prod DATE,
kind CHAR(10),
len INTERVAL HOUR TO MINUTE,
<programlisting>
CREATE TABLE distributors (
- did DECIMAL(03),
+ did DECIMAL(3),
name CHAR VARYING(40),
PRIMARY KEY(did)
);
<programlisting>
CREATE TABLE distributors (
- did DECIMAL(03) PRIMARY KEY,
+ did DECIMAL(3) PRIMARY KEY,
name VARCHAR(40)
);
</programlisting>
<programlisting>
CREATE TEMPORARY TABLE actors (
- id DECIMAL(03),
+ id DECIMAL(3),
name VARCHAR(40),
CONSTRAINT actor_id CHECK (id < 150)
) ON COMMIT DELETE ROWS;
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.6 1999/07/22 15:09:11 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.7 2000/07/22 04:30:27 momjian Exp $
Postgres documentation
-->
</para>
<para>
Refer to <command>CREATE TYPE</command> for
- inforamation on how to create types.
+ information on how to create types.
</para>
<para>
It is the user's responsibility to remove any operators,
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/fetch.sgml,v 1.11 2000/07/22 02:39:10 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/fetch.sgml,v 1.12 2000/07/22 04:30:27 momjian Exp $
Postgres documentation
-->
</computeroutput></term>
<listitem>
<para>
- <acronym>SQL92</acronym> allows one to repetatively retrieve the cursor
+ <acronym>SQL92</acronym> allows one to repetitively retrieve the cursor
at its "current position" using the syntax
<synopsis>
FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.20 2000/03/28 14:35:27 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.21 2000/07/22 04:30:27 momjian Exp $
Postgres documentation
-->
<para>
For example, an application runs a transaction at READ COMMITTED isolation
- level and needs to ensure the existance of data in a table for the
+ level and needs to ensure the existence of data in a table for the
duration of the
transaction. To achieve this you could use SHARE lock mode over the
table before querying. This will protect data from concurrent changes
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgctl-ref.sgml,v 1.5 2000/07/21 03:13:32 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgctl-ref.sgml,v 1.6 2000/07/22 04:30:27 momjian Exp $
Postgres documentation
-->
<para>
Immediate mode sends SIGUSR1
to the backends and lets them abort. In this case, database recovery
- will be neccessary on the next startup.
+ will be necessary on the next startup.
</para>
</listitem>
</varlistentry>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.31 2000/07/21 18:51:24 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.32 2000/07/22 04:30:27 momjian Exp $
Postgres documentation
-->
<replaceable class="PARAMETER">boolean_expr</replaceable>
can consist of any expression which evaluates to a boolean value.
- In many cases, this expression will be
+ In many cases, this expression will be:
<synopsis>
<replaceable class="PARAMETER">expr</replaceable> <replaceable class="PARAMETER">cond_op</replaceable> <replaceable class="PARAMETER">expr</replaceable>