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
d09f6f77
Commit
d09f6f77
authored
Jan 08, 2002
by
Tom Lane
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Minor wordsmithing.
parent
a6e704ce
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
7 deletions
+8
-7
doc/src/sgml/keywords.sgml
doc/src/sgml/keywords.sgml
+8
-7
No files found.
doc/src/sgml/keywords.sgml
View file @
d09f6f77
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/keywords.sgml,v 2.
4 2001/11/17 13:27:16 petere
Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/keywords.sgml,v 2.
5 2002/01/08 15:38:42 tgl
Exp $ -->
<appendix id="sql-keywords-appendix">
<title><acronym>SQL</acronym> Key Words</title>
...
...
@@ -17,12 +17,13 @@
<para>
SQL distinguishes between <firstterm>reserved</firstterm> and
<firstterm>non-reserved</firstterm> key words. Reserved key words
<firstterm>non-reserved</firstterm> key words. According to the standard,
reserved key words
are the only real key words; they are never allowed as identifiers.
Non-reserved key words only have a special meaning in particular
contexts and can be used as identifiers in other contexts. Most
non-reserved key words are actually the names of built-in tables
and functions specified by SQL
and t
he concept of non-reserved key
and functions specified by SQL
. T
he concept of non-reserved key
words essentially only exists to declare that some predefined meaning
is attached to a word in some contexts.
</para>
...
...
@@ -33,9 +34,9 @@
ranging from those that can never be used as an identifier to those
that have absolutely no special status in the parser as compared to
an ordinary identifier. (The latter is usually the case for
functions specified by SQL.)
SQL
reserved key words are not
functions specified by SQL.)
Even
reserved key words are not
completely reserved in <productname>PostgreSQL</productname>, but
can be used as column label
(as in
<literal>SELECT 55 AS
can be used as column label
s (for example,
<literal>SELECT 55 AS
CHECK</literal>, even though <token>CHECK</token> is a reserved key
word).
</para>
...
...
@@ -47,12 +48,12 @@
known to the parser but are allowed in most or all contexts where an
identifier is expected. Some key words that are otherwise
non-reserved cannot be used as function or data type names and are
marked accordingly. (
Some of these token
s represent built-in
marked accordingly. (
Most of these word
s represent built-in
functions or data types with special syntax. The function or type
is still available but it cannot be redefined by the user.) Labeled
<quote>reserved</quote> are those tokens that are only allowed as
<quote>AS</quote> column label names (and perhaps in very few other
contexts). Some reserved key words are a
vail
able as names for
contexts). Some reserved key words are a
llow
able as names for
functions; this is also shown in the table.
</para>
...
...
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