mirror of
https://github.com/postgres/postgres.git
synced 2025-12-21 05:21:08 +03:00
Replace ASCII-quotes with proper markup.
This commit is contained in:
Peter Eisentraut
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.23 2001/09/03 12:57:49 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.24 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -380,7 +380,7 @@ ERROR: <replaceable>reason</replaceable>
|
||||
<term>Signature</term>
|
||||
<listitem>
|
||||
<para>
|
||||
12-byte sequence "PGBCOPY\n\377\r\n\0" --- note that the null
|
||||
12-byte sequence <literal>PGBCOPY\n\377\r\n\0</> --- note that the null
|
||||
is a required part of the signature. (The signature is designed to allow
|
||||
easy identification of files that have been munged by a non-8-bit-clean
|
||||
transfer. This signature will be changed by newline-translation
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.14 2001/09/03 12:57:49 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.15 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -206,7 +206,7 @@ CREATE
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If the state transition function is declared "strict" in pg_proc,
|
||||
If the state transition function is declared <quote>strict</quote>,
|
||||
then it cannot be called with NULL inputs. With such a transition
|
||||
function, aggregate execution behaves as follows. NULL input values
|
||||
are ignored (the function is not called and the previous state value
|
||||
@@ -230,7 +230,7 @@ CREATE
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If the final function is declared "strict", then it will not
|
||||
If the final function is declared <quote>strict</quote>, then it will not
|
||||
be called when the ending state value is NULL; instead a NULL result
|
||||
will be output automatically. (Of course this is just the normal
|
||||
behavior of strict functions.) In any case the final function has
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_database.sgml,v 1.19 2001/09/03 12:57:49 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_database.sgml,v 1.20 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -186,11 +186,11 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable>
|
||||
as an environment variable name, which must be known to the
|
||||
server process. This way the database administrator can
|
||||
exercise control over locations in which databases can be created.
|
||||
(A customary choice is, e.g., '<envar>PGDATA2</envar>'.)
|
||||
(A customary choice is, e.g., <envar>PGDATA2</envar>.)
|
||||
If the server is compiled with <literal>ALLOW_ABSOLUTE_DBPATHS</literal>
|
||||
(not so by default), absolute path names, as identified by
|
||||
a leading slash
|
||||
(e.g., '<filename>/usr/local/pgsql/data</filename>'),
|
||||
(e.g., <filename>/usr/local/pgsql/data</filename>),
|
||||
are allowed as well.
|
||||
</para>
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.20 2001/09/03 12:57:49 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.21 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -185,19 +185,20 @@ CREATE
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
"$" cannot be defined as a single-character operator,
|
||||
<literal>$</literal> cannot be defined as a single-character operator,
|
||||
although it can be part of a multi-character operator name.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
"--" and "/*" cannot appear anywhere in an operator name,
|
||||
<literal>--</literal> and <literal>/*</literal> cannot appear anywhere in an operator name,
|
||||
since they will be taken as the start of a comment.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
A multi-character operator name cannot end in "+" or "-",
|
||||
A multi-character operator name cannot end in <literal>+</literal> or
|
||||
<literal>-</literal>,
|
||||
unless the name also contains at least one of these characters:
|
||||
<literallayout>
|
||||
~ ! @ # % ^ & | ` ? $
|
||||
@@ -214,7 +215,7 @@ CREATE
|
||||
<para>
|
||||
When working with non-SQL-standard operator names, you will usually
|
||||
need to separate adjacent operators with spaces to avoid ambiguity.
|
||||
For example, if you have defined a left-unary operator named "@",
|
||||
For example, if you have defined a left-unary operator named <literal>@</literal>,
|
||||
you cannot write <literal>X*@Y</literal>; you must write
|
||||
<literal>X* @Y</literal> to ensure that
|
||||
<productname>Postgres</productname> reads it as two operator names
|
||||
@@ -223,7 +224,7 @@ CREATE
|
||||
</note>
|
||||
</para>
|
||||
<para>
|
||||
The operator "!=" is mapped to "<>" on input, so these two names
|
||||
The operator <literal>!=</literal> is mapped to <literal><></literal> on input, so these two names
|
||||
are always equivalent.
|
||||
</para>
|
||||
<para>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.19 2001/09/03 12:57:49 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.20 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -270,7 +270,7 @@ SELECT last_value FROM <replaceable>seqname</replaceable>;
|
||||
that obtain numbers from the same sequence, a nextval operation
|
||||
is never rolled back; that is, once a value has been fetched it is
|
||||
considered used, even if the transaction that did the nextval later
|
||||
aborts. This means that aborted transactions may leave unused "holes"
|
||||
aborts. This means that aborted transactions may leave unused <quote>holes</quote>
|
||||
in the sequence of assigned values. setval operations are never
|
||||
rolled back, either.
|
||||
</para>
|
||||
@@ -315,7 +315,7 @@ SELECT last_value FROM <replaceable>seqname</replaceable>;
|
||||
<para>
|
||||
Each backend uses its own cache to store preallocated numbers.
|
||||
Numbers that are cached but not used in the current session will be
|
||||
lost, resulting in "holes" in the sequence.
|
||||
lost, resulting in <quote>holes</quote> in the sequence.
|
||||
</para>
|
||||
</refsect2>
|
||||
</refsect1>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.45 2001/09/03 12:57:49 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.46 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -236,7 +236,7 @@ ERROR: Relation '<replaceable class="parameter">table</replaceable>' already ex
|
||||
|
||||
<para>
|
||||
<command>CREATE TABLE</command> will enter a new, initially empty table
|
||||
into the current database. The table will be "owned" by the user issuing the
|
||||
into the current database. The table will be owned by the user issuing the
|
||||
command.
|
||||
</para>
|
||||
|
||||
@@ -1253,8 +1253,8 @@ ERROR: <replaceable class="parameter">name</replaceable> referential integrity
|
||||
|
||||
<para>
|
||||
A table constraint is an integrity constraint defined on one or
|
||||
more columns of a table. The four variations of "Table
|
||||
Constraint" are:
|
||||
more columns of a table. The four variations of <quote>Table
|
||||
Constraint</quote> are:
|
||||
<simplelist columns="1">
|
||||
<member>UNIQUE</member>
|
||||
<member>CHECK</member>
|
||||
@@ -1898,7 +1898,7 @@ CREATE GLOBAL TEMPORARY TABLE <replaceable class="parameter">table</replaceable>
|
||||
NULL clause
|
||||
</title>
|
||||
<para>
|
||||
The NULL "constraint" (actually a non-constraint) is a
|
||||
The NULL <quote>constraint</quote> (actually a non-constraint) is a
|
||||
<productname>Postgres</productname> extension to SQL92 that is
|
||||
included for symmetry with the NOT NULL clause (and for compatibility
|
||||
with some other RDBMSes). Since it is the
|
||||
@@ -1927,7 +1927,7 @@ CREATE GLOBAL TEMPORARY TABLE <replaceable class="parameter">table</replaceable>
|
||||
<!--
|
||||
I can't figure out why DEFAULT clause is different from what we already have.
|
||||
Perhaps because CURRENT_USER and CURRENT_DATE have specific types (currently
|
||||
the "name" type), if you aren't careful then the types won't match up with
|
||||
the <type>name</type> type), if you aren't careful then the types won't match up with
|
||||
the column. Not our problem...
|
||||
- Thomas 1998-08-16
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.15 2001/09/03 12:57:49 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.16 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -126,7 +126,7 @@ CREATE
|
||||
being inserted (for <command>INSERT</command> and
|
||||
<command>UPDATE</command> operations only). If
|
||||
the trigger fires after the event, all changes, including the
|
||||
last insertion, update, or deletion, are "visible" to the trigger.
|
||||
last insertion, update, or deletion, are <quote>visible</quote> to the trigger.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.21 2001/09/03 12:57:49 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.22 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -153,9 +153,9 @@ CREATE TYPE <replaceable class="parameter">typename</replaceable> ( INPUT = <rep
|
||||
<listitem>
|
||||
<para>
|
||||
Storage alignment requirement of the data type. If specified, must
|
||||
be '<literal>char</literal>', '<literal>int2</literal>',
|
||||
'<literal>int4</literal>', or '<literal>double</literal>';
|
||||
the default is '<literal>int4</literal>'.
|
||||
be <literal>char</literal>, <literal>int2</literal>,
|
||||
<literal>int4</literal>, or <literal>double</literal>;
|
||||
the default is <literal>int4</literal>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -165,9 +165,9 @@ CREATE TYPE <replaceable class="parameter">typename</replaceable> ( INPUT = <rep
|
||||
<listitem>
|
||||
<para>
|
||||
Storage technique for the data type. If specified, must
|
||||
be '<literal>plain</literal>', '<literal>external</literal>',
|
||||
'<literal>extended</literal>', or '<literal>main</literal>';
|
||||
the default is '<literal>plain</literal>'.
|
||||
be <literal>plain</literal>, <literal>external</literal>,
|
||||
<literal>extended</literal>, or <literal>main</literal>;
|
||||
the default is <literal>plain</literal>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -228,7 +228,7 @@ CREATE
|
||||
<replaceable class="parameter">output_function</replaceable>
|
||||
performs the reverse transformation. Both
|
||||
the input and output functions must be declared to take
|
||||
one or two arguments of type "<literal>opaque</literal>".
|
||||
one or two arguments of type <type>opaque</type>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -237,7 +237,7 @@ CREATE
|
||||
positive integer, or variable length,
|
||||
in which case Postgres assumes that the new type has the
|
||||
same format
|
||||
as the Postgres-supplied data type, "<literal>text</literal>".
|
||||
as the Postgres-supplied data type, <type>text</type>.
|
||||
To indicate that a type is variable length, set
|
||||
<replaceable class="parameter">internallength</replaceable>
|
||||
to <option>VARIABLE</option>.
|
||||
@@ -264,7 +264,7 @@ CREATE
|
||||
|
||||
<para>
|
||||
A default value is optionally available in case a user
|
||||
wants some specific bit pattern to mean "data not present."
|
||||
wants some specific bit pattern to mean <quote>data not present</quote>.
|
||||
Specify the default with the <literal>DEFAULT</literal> keyword.
|
||||
<comment>How does the user specify that bit pattern and associate
|
||||
it with the fact that the data is not present></comment>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.13 2001/09/03 12:57:49 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.14 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -210,9 +210,9 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks
|
||||
|
||||
<para>
|
||||
As an example, if a query returns a value of one from an integer column,
|
||||
you would get a string of '1' with a default cursor
|
||||
you would get a string of <literal>1</> with a default cursor
|
||||
whereas with a binary cursor you would get
|
||||
a 4-byte value equal to control-A ('^A').
|
||||
a 4-byte value equal to control-A (<literal>^A</literal>).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -227,7 +227,7 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks
|
||||
<emphasis><productname>Postgres</productname> does not resolve
|
||||
byte ordering or representation issues for binary cursors</emphasis>.
|
||||
Therefore, if your client machine and server machine use different
|
||||
representations (e.g., "big-endian" versus "little-endian"),
|
||||
representations (e.g., <quote>big-endian</quote> versus <quote>little-endian</quote>),
|
||||
you will probably not want your data returned in
|
||||
binary format.
|
||||
However, binary cursors may be a
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/fetch.sgml,v 1.15 2001/09/03 12:57:50 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/fetch.sgml,v 1.16 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -188,7 +188,7 @@ ERROR: FETCH/RELATIVE at current position is not supported
|
||||
<listitem>
|
||||
<para>
|
||||
<acronym>SQL92</acronym> allows one to repetitively retrieve the cursor
|
||||
at its "current position" using the syntax
|
||||
at its <quote>current position</quote> using the syntax
|
||||
<synopsis>
|
||||
FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>.
|
||||
</synopsis>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/initlocation.sgml,v 1.12 2001/09/03 12:57:50 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/initlocation.sgml,v 1.13 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -37,7 +37,7 @@ Postgres documentation
|
||||
which is referenced. See the examples at the end.
|
||||
</para>
|
||||
<para>
|
||||
In order to use this command you must be logged in (using 'su', for example)
|
||||
In order to use this command you must be logged in (using <command>su</command>, for example)
|
||||
as the database superuser.
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/notify.sgml,v 1.14 2001/09/03 12:57:50 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/notify.sgml,v 1.15 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -103,8 +103,8 @@ NOTIFY
|
||||
</para>
|
||||
<para>
|
||||
Commonly, the notify condition name is the same as the name of some table in
|
||||
the database, and the notify event essentially means "I changed this table,
|
||||
take a look at it to see what's new". But no such association is enforced by
|
||||
the database, and the notify event essentially means <quote>I changed this table,
|
||||
take a look at it to see what's new</quote>. But no such association is enforced by
|
||||
the <command>NOTIFY</command> and <command>LISTEN</command> commands. For
|
||||
example, a database designer could use several different condition names
|
||||
to signal different sorts of changes to a single table.
|
||||
@@ -137,7 +137,7 @@ NOTIFY
|
||||
after the transaction is completed (either committed or aborted). Again, the
|
||||
reasoning is that if a notify were delivered within a transaction that was
|
||||
later aborted, one would want the notification to be undone somehow---but
|
||||
the backend cannot "take back" a notify once it has sent it to the frontend.
|
||||
the backend cannot <quote>take back</quote> a notify once it has sent it to the frontend.
|
||||
So notify events are only delivered between transactions. The upshot of this
|
||||
is that applications using <command>NOTIFY</command> for real-time signaling
|
||||
should try to keep their transactions short.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.15 2001/09/03 12:57:50 petere Exp $ -->
|
||||
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.16 2001/09/13 15:55:24 petere Exp $ -->
|
||||
|
||||
<refentry id="APP-PGRESTORE">
|
||||
<docinfo>
|
||||
@@ -295,7 +295,7 @@
|
||||
<listitem>
|
||||
<para>
|
||||
Restore elements in <REPLACEABLE CLASS="PARAMETER">list-file</REPLACEABLE> only, and in the
|
||||
order they appear in the file. Lines can be moved and may also be commented out by placing a ';' at the
|
||||
order they appear in the file. Lines can be moved and may also be commented out by placing a <literal>;</literal> at the
|
||||
start of the line.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.59 2001/09/11 05:11:59 ishii Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.60 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -103,7 +103,7 @@ Postgres documentation
|
||||
<para>
|
||||
In normal operation, <application>psql</application> provides a prompt with
|
||||
the name of the database to which <application>psql</application> is currently
|
||||
connected, followed by the string "=>". For example,
|
||||
connected, followed by the string <literal>=></literal>. For example,
|
||||
<programlisting>
|
||||
$ <userinput>psql testdb</userinput>
|
||||
Welcome to psql, the PostgreSQL interactive terminal.
|
||||
@@ -1152,7 +1152,7 @@ lo_import 152801
|
||||
|
||||
<para>
|
||||
<programlisting>
|
||||
test=> <userinput>\z</userinput>
|
||||
test=> <userinput>\z</userinput>
|
||||
Access permissions for database "test"
|
||||
Relation | Access permissions
|
||||
----------+-------------------------------------
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.44 2001/09/03 12:57:50 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.45 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -268,7 +268,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be:
|
||||
specified expressions, keeping only the first row of each set of
|
||||
duplicates. The DISTINCT ON expressions are interpreted using the
|
||||
same rules as for ORDER BY items; see below.
|
||||
Note that "the first row" of each set is unpredictable
|
||||
Note that the <quote>first row</quote> of each set is unpredictable
|
||||
unless <command>ORDER BY</command> is used to ensure that the desired
|
||||
row appears first. For example,
|
||||
<programlisting>
|
||||
@@ -997,13 +997,13 @@ contains an explicit FROM clause.
|
||||
SELECT Clause
|
||||
</title>
|
||||
<para>
|
||||
In the <acronym>SQL92</acronym> standard, the optional keyword "AS"
|
||||
In the <acronym>SQL92</acronym> standard, the optional keyword <literal>AS</>
|
||||
is just noise and can be
|
||||
omitted without affecting the meaning.
|
||||
The <productname>Postgres</productname> parser requires this keyword when
|
||||
renaming output columns because the type extensibility features lead to
|
||||
parsing ambiguities
|
||||
in this context. "AS" is optional in FROM items, however.</para>
|
||||
in this context. <literal>AS</literal> is optional in FROM items, however.</para>
|
||||
|
||||
<para>
|
||||
The DISTINCT ON phrase is not part of <acronym>SQL92</acronym>.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.15 2001/09/03 12:57:50 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.16 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -95,7 +95,7 @@ UNLISTEN { <replaceable class="PARAMETER">notifyname</replaceable> | * }
|
||||
UNLISTEN cancels any existing registration of the current
|
||||
<productname>Postgres</productname> session as a listener on the notify
|
||||
condition <replaceable class="PARAMETER">notifyname</replaceable>.
|
||||
The special condition wildcard "*" cancels all listener registrations
|
||||
The special condition wildcard <literal>*</literal> cancels all listener registrations
|
||||
for the current session.
|
||||
</para>
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.16 2001/09/03 12:57:50 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.17 2001/09/13 15:55:24 petere Exp $
|
||||
Postgres documentation
|
||||
-->
|
||||
|
||||
@@ -152,7 +152,7 @@ UPDATE <replaceable class="parameter">#</replaceable>
|
||||
</title>
|
||||
|
||||
<para>
|
||||
Change word "Drama" with "Dramatic" on column kind:
|
||||
Change word <literal>Drama</> with <literal>Dramatic</> on column <structfield>kind</>:
|
||||
|
||||
<programlisting>
|
||||
UPDATE films
|
||||
|
||||
Reference in New Issue
Block a user