information_schema.key_column_usage.position_in_unique_constraint was

misdocumented as not being implemented.  In reality it has worked since
the release of 8.2.

diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml
index 7289e0bd456846cc1aabcced4de67a8321c293a3..da01c9cc5a71085eaf2dbb8ce85e251543393465 100644 (file)
--- a/doc/src/sgml/information_schema.sgml
+++ b/doc/src/sgml/information_schema.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  The Information Schema
@@ -2192,7 +2192,7 @@ ORDER BY c.ordinal_position;
       sql_identifier
       
        Name of the database that contains the table that contains the
-       column that is restricted by some constraint (always the
+       column that is restricted by this constraint (always the
        current database)
       
      
@@ -2202,7 +2202,7 @@ ORDER BY c.ordinal_position;
       sql_identifier
       
        Name of the schema that contains the table that contains the
-       column that is restricted by some constraint
+       column that is restricted by this constraint
       
      
 
@@ -2211,7 +2211,7 @@ ORDER BY c.ordinal_position;
       sql_identifier
       
        Name of the table that contains the column that is restricted
-       by some constraint
+       by this constraint
       
      
 
@@ -2219,7 +2219,7 @@ ORDER BY c.ordinal_position;
       column_name
       sql_identifier
       
-       Name of the column that is restricted by some constraint
+       Name of the column that is restricted by this constraint
       
      
 
@@ -2236,7 +2236,9 @@ ORDER BY c.ordinal_position;
       position_in_unique_constraint
       cardinal_number
       
-       Not yet implemented
+       For a foreign-key constraint, ordinal position of the referenced
+       column within its unique constraint (count starts at 1);
+       otherwise null