Re: constraints on composite types - Mailing list pgsql-general

From Michael Fuhr
Subject Re: constraints on composite types
Date
Msg-id 20050909153142.GA25183@winnie.fuhr.org
Whole thread Raw
In response to Re: constraints on composite types  (Roman Neuhauser <neuhauser@sigpipe.cz>)
List pgsql-general
On Fri, Sep 09, 2005 at 05:20:58PM +0200, Roman Neuhauser wrote:
> # mike@fuhr.org / 2005-09-09 09:10:30 -0600:
> > On Fri, Sep 09, 2005 at 10:39:58AM -0400, Tom Lane wrote:
> > > I don't believe you need the function -- this should be enough:
> > >
> > > CREATE UNIQUE INDEX t1_b_uniq ON t1 ((attr.foo));
> >
> > I was expecting that to work too, but it doesn't:
> >
> > ERROR:  relation "attr" does not exist
>
>     The manual says something to the effect of (table.col).subcol,
>     I'll need that schema-qualified as well, IOW (schema.table.col).subcol

This works:

CREATE UNIQUE INDEX t1_b_uniq ON t1 (((attr).foo));

--
Michael Fuhr

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: constraints on composite types
Next
From: snacktime
Date:
Subject: Re: per user logging