CVS HEAD doc won't compile due to broken mark up. Please someone
commit following patches if they are appropreate.
Also please do not commit broken sgml files without trying to compile
them.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
Index: array.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/array.sgml,v
retrieving revision 1.58
diff -c -r1.58 array.sgml
*** array.sgml 20 Feb 2007 14:54:47 -0000 1.58
--- array.sgml 2 Mar 2007 05:29:24 -0000
***************
*** 243,254 ****
(1 row)
</programlisting>
If any dimension is written as a slice, i.e contains a colon, then all
dimensions are treated as slices. If a dimension is missing, it is
assumed to be <literal>[1:1]</>. If a dimension has only a single
number (no colon), that dimension is treated as being from <literal>1</>
to the number specified. For example, <literal>[2]</> is treated as
! <literal>[1:2], as in this example:
<programlisting>
SELECT schedule[1:2][2] FROM sal_emp WHERE name = 'Bill';
--- 243,257 ----
(1 row)
</programlisting>
+ </para>
+
+ <para>
If any dimension is written as a slice, i.e contains a colon, then all
dimensions are treated as slices. If a dimension is missing, it is
assumed to be <literal>[1:1]</>. If a dimension has only a single
number (no colon), that dimension is treated as being from <literal>1</>
to the number specified. For example, <literal>[2]</> is treated as
! <literal>[1:2]</>, as in this example:
<programlisting>
SELECT schedule[1:2][2] FROM sal_emp WHERE name = 'Bill';
[EMAIL PROTECTED] sgml]$
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
