Re: constraints on composite types

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Richard Huxton <dev(at)archonet(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: constraints on composite types
Date: 2005-09-09 15:31:42
Message-ID: 20050909153142.GA25183@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Sep 09, 2005 at 05:20:58PM +0200, Roman Neuhauser wrote:
> # mike(at)fuhr(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message snacktime 2005-09-09 16:14:24 Re: per user logging
Previous Message Tom Lane 2005-09-09 15:29:24 Re: constraints on composite types