| From: | Roman Neuhauser <neuhauser(at)sigpipe(dot)cz> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | 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:20:58 |
| Message-ID: | 20050909152058.GA44851@isis.sigpipe.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
# 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
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-09-09 15:29:24 | Re: constraints on composite types |
| Previous Message | Michael Fuhr | 2005-09-09 15:10:30 | Re: constraints on composite types |