database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-12-15 02:22:24 +03:00
Code Activity

Spellchecking and such

Browse Source
This commit is contained in:
Peter Eisentraut
2006-10-23 18:10:32 +00:00
parent 033cb9d30b
commit 0f763503ff
35 changed files with 231 additions and 228 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/ref/alter_table.sgml
View File

@@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.91 2006/10/13 21:43:18 tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.92 2006/10/23 18:10:32 petere Exp $
PostgreSQL documentation
-->
@@ -740,7 +740,7 @@ ALTER TABLE foo
<para>
The same, when the column has a default expression that won't automatically
cast to the new datatype:
cast to the new data type:
<programlisting>
ALTER TABLE foo
ALTER COLUMN foo_timestamp DROP DEFAULT,

4
doc/src/sgml/ref/comment.sgml
View File

@@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/comment.sgml,v 1.32 2006/09/16 00:30:17 momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/comment.sgml,v 1.33 2006/10/23 18:10:32 petere Exp $
PostgreSQL documentation
-->
@@ -206,7 +206,7 @@ COMMENT ON
connected to a database can see all the comments for objects in
that database (although only superusers can change comments for
objects that they don't own). For shared objects such as
databases, roles, and tablespaces comments are stored gloablly
databases, roles, and tablespaces comments are stored globally
and any user connected to any database can see all the comments
for shared objects. Therefore, don't put security-critical
information in comments.

4
doc/src/sgml/ref/create_trigger.sgml
View File

@@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.44 2006/09/16 00:30:17 momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.45 2006/10/23 18:10:32 petere Exp $
PostgreSQL documentation
-->
@@ -258,7 +258,7 @@ CREATE TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTE
DELETE</literal> to always fire before the delete action, even a cascading
one. This is considered more consistent. There is also unpredictable
behavior when <literal>BEFORE</literal> triggers modify rows that are later
to be modified by referential actions. This can lead to contraint violations
to be modified by referential actions. This can lead to constraint violations
or stored data that does not honor the referential constraint.
</para>

4
doc/src/sgml/ref/drop_type.sgml
View File

@@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.28 2006/09/16 00:30:18 momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.29 2006/10/23 18:10:32 petere Exp $
PostgreSQL documentation
-->
@@ -94,7 +94,7 @@ DROP TYPE box;
<para>
This command is similar to the corresponding command in the SQL
standard, aapart from the <literal>IF EXISTS</>
standard, apart from the <literal>IF EXISTS</>
option, which is a <productname>PostgreSQL</> extension.
But note that the <command>CREATE TYPE</command> command
and the data type extension mechanisms in

4
doc/src/sgml/ref/insert.sgml
View File

@@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/insert.sgml,v 1.33 2006/09/18 19:54:01 tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/insert.sgml,v 1.34 2006/10/23 18:10:32 petere Exp $
PostgreSQL documentation
-->
@@ -234,7 +234,7 @@ INSERT INTO films DEFAULT VALUES;
</para>
<para>
To insert multiple rows using the multi-row <command>VALUES</> syntax:
To insert multiple rows using the multirow <command>VALUES</> syntax:
<programlisting>
INSERT INTO films (code, title, did, date_prod, kind) VALUES

16
doc/src/sgml/ref/pg_config-ref.sgml
View File

@@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.24 2006/09/16 00:30:19 momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.25 2006/10/23 18:10:32 petere Exp $ -->
<refentry id="app-pgconfig">
<refmeta>
@@ -177,7 +177,7 @@
<term><option>--cc</option></>
<listitem>
<para>
Print the value of the CC macro that was used for building
Print the value of the <varname>CC</varname> variable that was used for building
<productname>PostgreSQL</>. This shows the C compiler used.
</para>
</listitem>
@@ -187,7 +187,7 @@
<term><option>--cppflags</option></>
<listitem>
<para>
Print the value of the CPPFLAGS macro that was used for building
Print the value of the <varname>CPPFLAGS</varname> variable that was used for building
<productname>PostgreSQL</>. This shows C compiler switches needed
at preprocessing time (typically, <literal>-I</> switches).
</para>
@@ -198,7 +198,7 @@
<term><option>--cflags</option></>
<listitem>
<para>
Print the value of the CFLAGS macro that was used for building
Print the value of the <varname>CFLAGS</varname> variable that was used for building
<productname>PostgreSQL</>. This shows C compiler switches.
</para>
</listitem>
@@ -208,7 +208,7 @@
<term><option>--cflags_sl</option></>
<listitem>
<para>
Print the value of the CFLAGS_SL macro that was used for building
Print the value of the <varname>CFLAGS_SL</varname> variable that was used for building
<productname>PostgreSQL</>. This shows extra C compiler switches
used for building shared libraries.
</para>
@@ -219,7 +219,7 @@
<term><option>--ldflags</option></>
<listitem>
<para>
Print the value of the LDFLAGS macro that was used for building
Print the value of the <varname>LDFLAGS</varname> variable that was used for building
<productname>PostgreSQL</>. This shows linker switches.
</para>
</listitem>
@@ -229,7 +229,7 @@
<term><option>--ldflags_sl</option></>
<listitem>
<para>
Print the value of the LDFLAGS_SL macro that was used for building
Print the value of the <varname>LDFLAGS_SL</varname> variable that was used for building
<productname>PostgreSQL</>. This shows linker switches
used for building shared libraries.
</para>
@@ -240,7 +240,7 @@
<term><option>--libs</option></>
<listitem>
<para>
Print the value of the LIBS macro that was used for building
Print the value of the <varname>LIBS</varname> variable that was used for building
<productname>PostgreSQL</>. This normally contains <literal>-l</>
switches for external libraries linked into <productname>PostgreSQL</>.
</para>

4
doc/src/sgml/ref/pg_dump.sgml
View File

@@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.90 2006/10/09 23:36:58 tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.91 2006/10/23 18:10:32 petere Exp $
PostgreSQL documentation
-->
@@ -748,7 +748,7 @@ CREATE DATABASE foo WITH TEMPLATE template0;
</para>
<para>
Because <application>pg_dump</application> is used to tranfer data
Because <application>pg_dump</application> is used to transfer data
to newer versions of <productname>PostgreSQL</>, the output of
<application>pg_dump</application> can be loaded into
newer <productname>PostgreSQL</> databases. It also can read older

4
doc/src/sgml/ref/psql-ref.sgml
View File

@@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.171 2006/10/09 23:31:29 tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.172 2006/10/23 18:10:32 petere Exp $
PostgreSQL documentation
-->
@@ -2772,7 +2772,7 @@ Field separator is "oo".
<listitem>
<para>
Set the console font to <quote>Lucida Console</>, because the
Set the console font to <literal>Lucida Console</>, because the
raster font does not work with the ANSI code page.
</para>
</listitem>

6
doc/src/sgml/ref/values.sgml
View File

@@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/values.sgml,v 1.1 2006/09/18 19:54:01 tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/values.sgml,v 1.2 2006/10/23 18:10:32 petere Exp $
PostgreSQL documentation
-->
@@ -202,9 +202,9 @@ UPDATE employees SET salary = salary * v.increase
<para>
When <command>VALUES</> is used in <command>INSERT</>, the values are all
automatically coerced to the datatype of the corresponding destination
automatically coerced to the data type of the corresponding destination
column. When it's used in other contexts, it may be necessary to specify
the correct datatype. If the entries are all quoted literal constants,
the correct data type. If the entries are all quoted literal constants,
coercing the first is sufficient to determine the assumed type for all:
<programlisting>