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
0e9c1b1c
Commit
0e9c1b1c
authored
Dec 19, 2009
by
Tom Lane
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Sigh, I managed to break the no-links-in-plain-text-docs rule too...
parent
ce1489fa
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
9 deletions
+9
-9
doc/src/sgml/release-8.5.sgml
doc/src/sgml/release-8.5.sgml
+9
-9
No files found.
doc/src/sgml/release-8.5.sgml
View file @
0e9c1b1c
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.5.sgml,v 1.1
2 2009/12/19 02:38:54
tgl Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.5.sgml,v 1.1
3 2009/12/19 05:37:01
tgl Exp $ -->
<sect1 id="release-8-5">
<sect1 id="release-8-5">
<title>Release 8.5alpha3</title>
<title>Release 8.5alpha3</title>
...
@@ -686,8 +686,8 @@
...
@@ -686,8 +686,8 @@
meant, sometimes resulting in surprising behavior. Now, PL/pgSQL
meant, sometimes resulting in surprising behavior. Now, PL/pgSQL
can assume the variable is meant, or assume the table column is
can assume the variable is meant, or assume the table column is
meant, or throw an error in ambiguous cases. For safety the default
meant, or throw an error in ambiguous cases. For safety the default
is to throw error. To configure this see <
xref
is to throw error. To configure this see <
link
linkend="plpgsql-var-subst">.</emphasis>
linkend="plpgsql-var-subst">
the PL/pgSQL documentation</link>
.</emphasis>
</para>
</para>
<para>
<para>
<emphasis>Error reporting is much nicer: it no longer shows edited
<emphasis>Error reporting is much nicer: it no longer shows edited
...
@@ -697,12 +697,12 @@
...
@@ -697,12 +697,12 @@
<para>
<para>
<emphasis>Note that this change affects the set of keywords that are
<emphasis>Note that this change affects the set of keywords that are
reserved in PL/pgSQL (i.e., cannot be the name of a PL/pgSQL
reserved in PL/pgSQL (i.e., cannot be the name of a PL/pgSQL
variable). Now, all keywords shown as reserved in <
xref
variable). Now, all keywords shown as reserved in <
link
linkend="sql-keywords-appendix">
are reserved for PL/pgSQL purposes
linkend="sql-keywords-appendix">
Appendix C</link> are reserved for
as well. However, many PL/pgSQL-only keywords that were formerly
PL/pgSQL purposes as well. However, many PL/pgSQL-only keywords
t
reated as reserved no longer are. As in regular SQL, you can
t
hat were formerly treated as reserved no longer are. As in regular
double-quote a variable's name if you want to use a name that
SQL, you can double-quote a variable's name if you want to use a
conflicts with a reserved keyword.</emphasis>
name that
conflicts with a reserved keyword.</emphasis>
</para>
</para>
</listitem>
</listitem>
<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