Minor SGML style police work.

This commit is contained in:
Neil Conway 2006-02-18 23:14:45 +00:00
parent 3228a92ccd
commit 8c5dfbabff
5 changed files with 46 additions and 41 deletions

View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.54 2006/02/12 19:11:00 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.55 2006/02/18 23:14:45 neilc Exp $ -->
<chapter id="ddl"> <chapter id="ddl">
<title>Data Definition</title> <title>Data Definition</title>
@ -77,10 +77,11 @@
</indexterm> </indexterm>
<para> <para>
To create a table, you use the aptly named <command>CREATE To create a table, you use the aptly named <xref
TABLE</command> command. In this command you specify at least a linkend="sql-createtable" endterm="sql-createtable-title"> command.
name for the new table, the names of the columns and the data type In this command you specify at least a name for the new table, the
of each column. For example: names of the columns and the data type of each column. For
example:
<programlisting> <programlisting>
CREATE TABLE my_first_table ( CREATE TABLE my_first_table (
first_column text, first_column text,
@ -136,8 +137,9 @@ CREATE TABLE products (
</indexterm> </indexterm>
<para> <para>
If you no longer need a table, you can remove it using the If you no longer need a table, you can remove it using the <xref
<command>DROP TABLE</command> command. For example: linkend="sql-droptable" endterm="sql-droptable-title"> command.
For example:
<programlisting> <programlisting>
DROP TABLE my_first_table; DROP TABLE my_first_table;
DROP TABLE products; DROP TABLE products;
@ -1487,9 +1489,9 @@ REVOKE ALL ON accounts FROM PUBLIC;
</indexterm> </indexterm>
<para> <para>
To create a schema, use the command <command>CREATE To create a schema, use the <xref linkend="sql-createschema"
SCHEMA</command>. Give the schema a name of your choice. For endterm="sql-createschema-title"> command. Give the schema a name
example: of your choice. For example:
<programlisting> <programlisting>
CREATE SCHEMA myschema; CREATE SCHEMA myschema;
</programlisting> </programlisting>

View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/dml.sgml,v 1.12 2005/03/17 20:24:34 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/dml.sgml,v 1.13 2006/02/18 23:14:45 neilc Exp $ -->
<chapter id="dml"> <chapter id="dml">
<title>Data Manipulation</title> <title>Data Manipulation</title>
@ -39,7 +39,7 @@
<para> <para>
To create a new row, use the <xref linkend="sql-insert" To create a new row, use the <xref linkend="sql-insert"
xreflabel="sql-insert-title"> command. The command requires the endterm="sql-insert-title"> command. The command requires the
table name and a value for each of the columns of the table. For table name and a value for each of the columns of the table. For
example, consider the products table from <xref linkend="ddl">: example, consider the products table from <xref linkend="ddl">:
<programlisting> <programlisting>
@ -95,12 +95,12 @@ INSERT INTO products DEFAULT VALUES;
<tip> <tip>
<para> <para>
To do <quote>bulk loads</quote>, that is, inserting a lot of data, When inserting a lot of data at the same time, considering using
take a look at the <xref linkend="sql-copy" the <xref linkend="sql-copy" endterm="sql-copy-title"> command.
endterm="sql-copy-title"> command. It is not as flexible as the It is not as flexible as the <xref linkend="sql-insert"
<xref linkend="sql-insert" endterm="sql-insert-title"> command, endterm="sql-insert-title"> command, but is more efficient. Refer
but is more efficient. Refer to <xref linkend="populate"> for more to <xref linkend="populate"> for more information on improving
information on improving bulk loading performance. bulk loading performance.
</para> </para>
</tip> </tip>
</sect1> </sect1>
@ -224,11 +224,10 @@ UPDATE mytable SET a = 5, b = 3, c = 1 WHERE a &gt; 0;
</para> </para>
<para> <para>
You use the <xref linkend="sql-delete" You use the <xref linkend="sql-delete" endterm="sql-delete-title">
xreflabel="sql-delete-title"> command to remove rows; the syntax is command to remove rows; the syntax is very similar to the
very similar to the <command>UPDATE</command> command. For <command>UPDATE</command> command. For instance, to remove all
instance, to remove all rows from the products table that have a rows from the products table that have a price of 10, use
price of 10, use
<programlisting> <programlisting>
DELETE FROM products WHERE price = 10; DELETE FROM products WHERE price = 10;
</programlisting> </programlisting>

View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.86 2006/02/12 06:37:05 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.87 2006/02/18 23:14:45 neilc Exp $
--> -->
<chapter id="plpgsql"> <chapter id="plpgsql">
@ -1594,7 +1594,7 @@ SELECT * FROM some_func();
allow users to define set-returning functions allow users to define set-returning functions
that do not have this limitation. Currently, the point at that do not have this limitation. Currently, the point at
which data begins being written to disk is controlled by the which data begins being written to disk is controlled by the
<xref linkend="guc-work-mem" xreflabel="work_mem"> <xref linkend="guc-work-mem">
configuration variable. Administrators who have sufficient configuration variable. Administrators who have sufficient
memory to store larger result sets in memory should consider memory to store larger result sets in memory should consider
increasing this parameter. increasing this parameter.
@ -3642,11 +3642,12 @@ $$ LANGUAGE plpgsql;
<para> <para>
<productname>PostgreSQL</> gives you two function creation <productname>PostgreSQL</> gives you two function creation
modifiers to optimize execution: <quote>volatility</> (whether the modifiers to optimize execution: <quote>volatility</> (whether
function always returns the same result when given the same the function always returns the same result when given the same
arguments) and <quote>strictness</quote> (whether the arguments) and <quote>strictness</quote> (whether the function
function returns null if any argument is null). Consult the returns null if any argument is null). Consult the <xref
<xref linkend="sql-createfunction"> reference page for details. linkend="sql-createfunction" endterm="sql-createfunction-title">
reference page for details.
</para> </para>
<para> <para>

View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/queries.sgml,v 1.34 2005/05/08 03:08:05 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/queries.sgml,v 1.35 2006/02/18 23:14:45 neilc Exp $ -->
<chapter id="queries"> <chapter id="queries">
<title>Queries</title> <title>Queries</title>
@ -24,8 +24,9 @@
<para> <para>
The process of retrieving or the command to retrieve data from a The process of retrieving or the command to retrieve data from a
database is called a <firstterm>query</firstterm>. In SQL the database is called a <firstterm>query</firstterm>. In SQL the
<command>SELECT</command> command is used to specify queries. The <xref linkend="sql-select" endterm="sql-select-title"> command is
general syntax of the <command>SELECT</command> command is used to specify queries. The general syntax of the
<command>SELECT</command> command is
<synopsis> <synopsis>
SELECT <replaceable>select_list</replaceable> FROM <replaceable>table_expression</replaceable> <optional><replaceable>sort_specification</replaceable></optional> SELECT <replaceable>select_list</replaceable> FROM <replaceable>table_expression</replaceable> <optional><replaceable>sort_specification</replaceable></optional>
</synopsis> </synopsis>

View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/ref/alter_function.sgml,v 1.10 2005/11/01 21:09:50 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/ref/alter_function.sgml,v 1.11 2006/02/18 23:14:45 neilc Exp $
PostgreSQL documentation PostgreSQL documentation
--> -->
@ -151,8 +151,8 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
null. <literal>RETURNS NULL ON NULL INPUT</literal> or null. <literal>RETURNS NULL ON NULL INPUT</literal> or
<literal>STRICT</literal> changes the function so that it is not <literal>STRICT</literal> changes the function so that it is not
invoked if any of its arguments are null; instead, a null result invoked if any of its arguments are null; instead, a null result
is assumed automatically. See <xref is assumed automatically. See <xref linkend="sql-createfunction"
linkend="sql-createfunction"> for more information. endterm="sql-createfunction-title"> for more information.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -164,8 +164,9 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
<listitem> <listitem>
<para> <para>
Change the volatility of the function to the specified Change the volatility of the function to the specified setting.
setting. See <xref linkend="sql-createfunction"> for details. See <xref linkend="sql-createfunction"
endterm="sql-createfunction-title"> for details.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -178,8 +179,9 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
<para> <para>
Change whether the function is a security definer or not. The Change whether the function is a security definer or not. The
key word <literal>EXTERNAL</literal> is ignored for SQL key word <literal>EXTERNAL</literal> is ignored for SQL
conformance. See <xref linkend="sql-createfunction"> for more conformance. See <xref linkend="sql-createfunction"
information about this capability. endterm="sql-createfunction-title"> for more information about
this capability.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>