Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
4996eea8
Commit
4996eea8
authored
Feb 19, 2003
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
This patch includes more SGML markup fixes as well as a few minor
additions to the docs. Neil Conway
parent
aca86479
Changes
5
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
5 changed files
with
262 additions
and
230 deletions
+262
-230
doc/src/sgml/ddl.sgml
doc/src/sgml/ddl.sgml
+5
-5
doc/src/sgml/ref/create_table.sgml
doc/src/sgml/ref/create_table.sgml
+7
-4
doc/src/sgml/ref/create_type.sgml
doc/src/sgml/ref/create_type.sgml
+5
-4
doc/src/sgml/rules.sgml
doc/src/sgml/rules.sgml
+239
-211
doc/src/sgml/syntax.sgml
doc/src/sgml/syntax.sgml
+6
-6
No files found.
doc/src/sgml/ddl.sgml
View file @
4996eea8
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ddl.sgml,v 1.1
0 2002/11/15 03:11:15
momjian Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ddl.sgml,v 1.1
1 2003/02/19 03:13:24
momjian Exp $ -->
<chapter id="ddl">
<chapter id="ddl">
<title>Data Definition</title>
<title>Data Definition</title>
...
@@ -189,7 +189,7 @@ DROP TABLE products;
...
@@ -189,7 +189,7 @@ DROP TABLE products;
individual table a row came from. The
individual table a row came from. The
<structfield>tableoid</structfield> can be joined against the
<structfield>tableoid</structfield> can be joined against the
<structfield>oid</structfield> column of
<structfield>oid</structfield> column of
<
classname>pg_class</class
name> to obtain the table name.
<
structname>pg_class</struct
name> to obtain the table name.
</para>
</para>
</listitem>
</listitem>
</varlistentry>
</varlistentry>
...
@@ -904,9 +904,9 @@ WHERE c.altitude > 500;
...
@@ -904,9 +904,9 @@ WHERE c.altitude > 500;
139798 | Madison | 845
139798 | Madison | 845
</programlisting>
</programlisting>
(If you try to reproduce this example, you will probably get
different
(If you try to reproduce this example, you will probably get
numeric OIDs.) By doing a join with pg_class you can see the actual table
different numeric OIDs.) By doing a join with
names:
<structname>pg_class</> you can see the actual table
names:
<programlisting>
<programlisting>
SELECT p.relname, c.name, c.altitude
SELECT p.relname, c.name, c.altitude
...
...
doc/src/sgml/ref/create_table.sgml
View file @
4996eea8
<!--
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.6
1 2003/01/19 00:13:29
momjian Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.6
2 2003/02/19 03:13:25
momjian Exp $
PostgreSQL documentation
PostgreSQL documentation
-->
-->
...
@@ -230,7 +230,10 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is:
...
@@ -230,7 +230,10 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is:
for large tables, since it will reduce OID consumption and
for large tables, since it will reduce OID consumption and
thereby postpone wraparound of the 32-bit OID counter. Once the
thereby postpone wraparound of the 32-bit OID counter. Once the
counter wraps around, uniqueness of OIDs can no longer be
counter wraps around, uniqueness of OIDs can no longer be
assumed, which considerably reduces their usefulness.
assumed, which considerably reduces their usefulness. Specifying
<literal>WITHOUT OIDS</literal> also reduces the space required
to store the table on disk by 4 bytes per row of the table,
thereby improving performance.
</para>
</para>
</listitem>
</listitem>
</varlistentry>
</varlistentry>
...
@@ -881,8 +884,8 @@ CREATE ASSERTION <replaceable>name</replaceable> CHECK ( <replaceable>condition<
...
@@ -881,8 +884,8 @@ CREATE ASSERTION <replaceable>name</replaceable> CHECK ( <replaceable>condition<
<!--
<!--
<para>
<para>
Domain constraints are defined by
CREATE DOMAIN or ALTER DOMAIN
Domain constraints are defined by
<command>CREATE
statements:
DOMAIN</command> or <command>ALTER DOMAIN</command>
statements:
</para>
</para>
<para>
<para>
Domain constraint:
Domain constraint:
...
...
doc/src/sgml/ref/create_type.sgml
View file @
4996eea8
<!--
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.3
8 2003/01/19 00:13:29
momjian Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.3
9 2003/02/19 03:13:25
momjian Exp $
PostgreSQL documentation
PostgreSQL documentation
-->
-->
...
@@ -218,7 +218,8 @@ CREATE TYPE
...
@@ -218,7 +218,8 @@ CREATE TYPE
<para>
<para>
The first form of <command>CREATE TYPE</command> creates a new base type
The first form of <command>CREATE TYPE</command> creates a new base type
(scalar type). It requires the
(scalar type). It requires the
registration of two functions (using CREATE FUNCTION) before defining the
registration of two functions (using <command>CREATE
FUNCTION</command>) before defining the
type. The representation of a new base type is determined by
type. The representation of a new base type is determined by
<replaceable class="parameter">input_function</replaceable>, which
<replaceable class="parameter">input_function</replaceable>, which
converts the type's external representation to an internal
converts the type's external representation to an internal
...
@@ -400,8 +401,8 @@ CREATE TYPE
...
@@ -400,8 +401,8 @@ CREATE TYPE
<para>
<para>
User-defined type names cannot begin with the underscore character
User-defined type names cannot begin with the underscore character
(<quote><literal>_</literal></quote>) and can only be 62
(<quote><literal>_</literal></quote>) and can only be 62
characters long (or in general <
literal>NAMEDATALEN-2</>
, rather than
characters long (or in general <
symbol>NAMEDATALEN</symbol> - 2
, rather than
the <
literal>NAMEDATALEN-1</>
characters allowed for other names).
the <
symbol>NAMEDATALEN</symbol> - 1
characters allowed for other names).
Type names beginning with underscore are
Type names beginning with underscore are
reserved for internally-created array type names.
reserved for internally-created array type names.
</para>
</para>
...
...
doc/src/sgml/rules.sgml
View file @
4996eea8
This diff is collapsed.
Click to expand it.
doc/src/sgml/syntax.sgml
View file @
4996eea8
<!--
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.7
4 2002/11/15 03:11:17
momjian Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.7
5 2003/02/19 03:13:24
momjian Exp $
-->
-->
<chapter id="sql-syntax">
<chapter id="sql-syntax">
...
@@ -121,9 +121,9 @@ INSERT INTO MY_TABLE VALUES (3, 'hi there');
...
@@ -121,9 +121,9 @@ INSERT INTO MY_TABLE VALUES (3, 'hi there');
characters of an identifier; longer names can be written in
characters of an identifier; longer names can be written in
commands, but they will be truncated. By default,
commands, but they will be truncated. By default,
<symbol>NAMEDATALEN</symbol> is 64 so the maximum identifier
<symbol>NAMEDATALEN</symbol> is 64 so the maximum identifier
length is 63
(but at the time <productname>PostgreSQL</> is built,
length is 63
. If this limit is problematic, it can be raised by
<symbol>NAMEDATALEN</symbol> can be changed
in
changing the <symbol>NAMEDATALEN</symbol> constant
in
<filename>src/include/postgres_ext.h</filename>
)
.
<filename>src/include/postgres_ext.h</filename>.
</para>
</para>
<para>
<para>
...
@@ -541,8 +541,8 @@ CAST ( '<replaceable>string</replaceable>' AS <replaceable>type</replaceable> )
...
@@ -541,8 +541,8 @@ CAST ( '<replaceable>string</replaceable>' AS <replaceable>type</replaceable> )
<para>
<para>
A dollar sign (<literal>$</literal>) followed by digits is used
A dollar sign (<literal>$</literal>) followed by digits is used
to represent the positional parameters in the body of a function
to represent the positional parameters in the body of a function
definition
. In other contexts the dollar sign may be part of an
definition
or a prepared statement. In other contexts the
operator name.
dollar sign may be part of an
operator name.
</para>
</para>
</listitem>
</listitem>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment