Tom Lane wrote:
> Gerardo Herzig <gherzig@fmed.uba.ar> writes:
>> Hi all. Im failing while trying to obtain some metainfo from
>> information_schema. Acording to the docs, constraint_column_usage and
>> key_column_usage views contains some information about constraints and
>> indexes.
>
> No, they contain information about constraints, period. How did you
> create those indexes? If you made them via SQL-standard PRIMARY KEY or
> UNIQUE constraint syntax, they should show in the information_schema.
> Otherwise not.
>
> regards, tom lane
>
Well, i just dont get it. Official docs from 8.2 says:
"""The view key_column_usage identifies all columns in the current
database that are restricted by some *unique*, *primary key*, or foreign
key constraint. Check constraints are not included in this view. Only
those columns are shown that the current user has access to, by way of
being the owner or having some privilege.
"""
Well, damn, lets create some UNIQUE
edatos=# CREATE UNIQUE INDEX aluestud_alu_cod_anifm on aluestud (alucod,
codcarr1, anifm);
CREATE INDEX
edatos=#\d aluestud
[...]
Indexes: "estud_idx1" PRIMARY KEY, btree (alucod, codcarr1) "aluestud_alu_cod_anifm" UNIQUE, btree (alucod,
codcarr1,anifm)
And...
edatos=# select table_name, constraint_name, column_name from
information_schema.key_column_usage where table_name='aluestud';table_name | constraint_name | column_name
------------+-----------------+-------------aluestud | estud_idx1 | alucodaluestud | estud_idx1 |
codcarr1
(2 rows)
Damn, im that idiot? Or should i get the UNIQUE i have just defined also?