Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 79abc3b

Browse files
committed
Add explicit note that empty-string array element values now have to
be written with quotes. Minor copy-editing too.
1 parent 50742ae commit 79abc3b

File tree

1 file changed

+27
-11
lines changed

1 file changed

+27
-11
lines changed

doc/src/sgml/release.sgml

Lines changed: 27 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.292 2004/08/27 02:09:18 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.293 2004/08/30 00:33:52 tgl Exp $
33
-->
44

55
<appendix id="release">
@@ -327,11 +327,13 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.292 2004/08/27 02:09:18 momjian
327327

328328
<listitem>
329329
<para>
330-
Syntax checking of array input processing has been tighened up
330+
Syntax checking of array input values has been tightened up
331331
considerably. Junk that was previously allowed in odd places with
332-
odd results now causes an ERROR. Also changed behavior with respect
333-
to whitespace surrounding array elements; trailing whitespace is now
334-
ignored as well as leading whitespace (which has always been ignored).
332+
odd results now causes an ERROR. Empty-string element values must
333+
now be written as <literal>""</>, rather than writing nothing.
334+
Also changed behavior with respect to whitespace surrounding array
335+
elements: trailing whitespace is now ignored, for symmetry with leading
336+
whitespace (which has always been ignored).
335337
</para>
336338
</listitem>
337339
</itemizedlist>
@@ -1186,7 +1188,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.292 2004/08/27 02:09:18 momjian
11861188

11871189
<listitem>
11881190
<para>
1189-
Reject non-rectangular array literals as erroneous (Joe)
1191+
Reject non-rectangular array values as erroneous (Joe)
11901192
</para>
11911193
<para>
11921194
Formerly, <literal>array_in</literal> would silently build a
@@ -1196,11 +1198,25 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.292 2004/08/27 02:09:18 momjian
11961198

11971199
<listitem>
11981200
<para>
1199-
Syntax checking of array input processing considerably tighened up (Joe)
1201+
Syntax checking of array input values considerably tightened up (Joe)
12001202
</para>
12011203
<para>
12021204
Junk that was previously allowed in odd places with odd results now
1203-
causes an ERROR.
1205+
causes an ERROR: for example, non-whitespace after the closing
1206+
right brace.
1207+
</para>
1208+
</listitem>
1209+
1210+
<listitem>
1211+
<para>
1212+
Empty-string array element values must now be written as
1213+
<literal>""</>, rather than writing nothing (Joe)
1214+
</para>
1215+
<para>
1216+
Formerly, both ways of writing an empty-string element value were
1217+
allowed, but now a quoted empty string is required. The case where
1218+
nothing at all appears will probably be taken over to mean a NULL
1219+
element value in some future release.
12041220
</para>
12051221
</listitem>
12061222

@@ -1210,14 +1226,14 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.292 2004/08/27 02:09:18 momjian
12101226
</para>
12111227
<para>
12121228
Formerly leading whitespace was ignored, but trailing whitespace
1213-
between an element and the delimiter or right brace was significant.
1214-
Now trailing whitespace is also ignored.
1229+
between an element value and the delimiter or right brace was
1230+
significant. Now trailing whitespace is also ignored.
12151231
</para>
12161232
</listitem>
12171233

12181234
<listitem>
12191235
<para>
1220-
Emit array literals with explicit array bounds when lower bound is not one
1236+
Emit array values with explicit array bounds when lower bound is not one
12211237
(Joe)
12221238
</para>
12231239
</listitem>

0 commit comments

Comments
 (0)