database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-29 13:56:47 +03:00
Code

Improve documentation for odd array slice behavior.

Browse Source
This commit is contained in:
Bruce Momjian 2008-03-26 14:43:20 +00:00
parent c22de3989b
commit 9469d083e5
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/array.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/array.sgml,v 1.62 2007/06/07 14:49:56 tgl Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/array.sgml,v 1.63 2008/03/26 14:43:20 momjian Exp $ -->
<sect1 id="arrays"> <sect1 id="arrays">
<title>Arrays</title> <title>Arrays</title>
@ -258,6 +258,9 @@ SELECT schedule[1:2][2] FROM sal_emp WHERE name = 'Bill';
{{meeting,lunch},{training,presentation}} {{meeting,lunch},{training,presentation}}
(1 row) (1 row)
</programlisting> </programlisting>
To avoid confusion with slices, use slice syntax for all dimmension
references, e.g. <literal>[1:2][1:1]</>, not <literal>[2][1:1]</>.
</para> </para>
<para> <para>
@ -275,7 +278,8 @@ SELECT schedule[1:2][2] FROM sal_emp WHERE name = 'Bill';
any of the subscript expressions are null. However, in other corner any of the subscript expressions are null. However, in other corner
cases such as selecting an array slice that cases such as selecting an array slice that
is completely outside the current array bounds, a slice expression is completely outside the current array bounds, a slice expression
yields an empty (zero-dimensional) array instead of null. yields an empty (zero-dimensional) array instead of null. (This
does not match non-slice behavior and is done for historical reasons.)
If the requested slice partially overlaps the array bounds, then it If the requested slice partially overlaps the array bounds, then it
is silently reduced to just the overlapping region. is silently reduced to just the overlapping region.
</para> </para>