From 5eb2076c3c510819ff4dfadf74be7ab7736900b2 Mon Sep 17 00:00:00 2001
From: Tom Lane
Date: Sat, 24 Jan 2004 23:06:41 +0000
Subject: Fix problems with dropped columns in pltcl triggers, per report from
 Patrick Samson.

---
 doc/src/sgml/pltcl.sgml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

(limited to 'doc/src')

diff --git a/doc/src/sgml/pltcl.sgml b/doc/src/sgml/pltcl.sgml
index 7942d42af39..b5f286bd1e5 100644
--- a/doc/src/sgml/pltcl.sgml
+++ b/doc/src/sgml/pltcl.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/pltcl.sgml,v 2.26.2.1 2003/11/12 20:05:14 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/pltcl.sgml,v 2.26.2.2 2004/01/24 23:06:41 tgl Exp $
 -->
 
  <chapter id="pltcl">
@@ -516,7 +516,10 @@ SELECT 'doesn''t' AS ret
          element. So looking up a column name in the list with <application>Tcl</>'s
          <function>lsearch</> command returns the element's number starting
 	 with 1 for the first column, the same way the columns are customarily
-	 numbered in <productname>PostgreSQL</productname>.
+	 numbered in <productname>PostgreSQL</productname>.  (Empty list
+	 elements also appear in the positions of columns that have been
+	 dropped, so that the attribute numbering is correct for columns
+	 to their right.)
 	</para>
        </listitem>
       </varlistentry>
-- 
cgit v1.2.3