Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
0e9c1b1c
Commit
0e9c1b1c
authored
15 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
Sigh, I managed to break the no-links-in-plain-text-docs rule too...
parent
ce1489fa
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/release-8.5.sgml
+9
-9
9 additions, 9 deletions
doc/src/sgml/release-8.5.sgml
with
9 additions
and
9 deletions
doc/src/sgml/release-8.5.sgml
+
9
−
9
View file @
0e9c1b1c
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.5.sgml,v 1.1
2
2009/12/19 0
2
:3
8:54
tgl Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.5.sgml,v 1.1
3
2009/12/19 0
5
:3
7:01
tgl Exp $ -->
<sect1 id="release-8-5">
<title>Release 8.5alpha3</title>
...
...
@@ -686,8 +686,8 @@
meant, sometimes resulting in surprising behavior. Now, PL/pgSQL
can assume the variable is meant, or assume the table column is
meant, or throw an error in ambiguous cases. For safety the default
is to throw error. To configure this see <
xref
linkend="plpgsql-var-subst">.</emphasis>
is to throw error. To configure this see <
link
linkend="plpgsql-var-subst">
the PL/pgSQL documentation</link>
.</emphasis>
</para>
<para>
<emphasis>Error reporting is much nicer: it no longer shows edited
...
...
@@ -697,12 +697,12 @@
<para>
<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
variable). Now, all keywords shown as reserved in <
xref
linkend="sql-keywords-appendix"> are reserved for
PL/pgSQL purposes
as well. However, many PL/pgSQL-only keywords
that were formerly
treated as reserved no longer are. As in regular
SQL, you can
double-quote a variable's name if you want to use a
name that
conflicts with a reserved keyword.</emphasis>
variable). Now, all keywords shown as reserved in <
link
linkend="sql-keywords-appendix">
Appendix C</link>
are reserved for
PL/pgSQL purposes
as well. However, many PL/pgSQL-only keywords
that were formerly
treated as reserved no longer are. As in regular
SQL, you can
double-quote a variable's name if you want to use a
name that
conflicts with a reserved keyword.</emphasis>
</para>
</listitem>
<listitem>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment