From: | MargaretGillon(at)chromalloy(dot)com |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Unique constraint or index, case insensitive, on multiple |
Date: | 2006-04-06 18:41:01 |
Message-ID: | OF080D0C37.029F8DAD-ON88257148.0066595D-88257148.0066A042@CHROMALLOY.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote on 04/06/2006 11:33:57 AM:
> MargaretGillon(at)chromalloy(dot)com writes:
> > CREATE UNIQUE INDEX resource_refullname
> > ON resource USING btree (redtid, (upper(refullname) text_ops));
>
> You need something newer than PG 7.3 to do that. 7.3 can't handle
> functional indexes with more than one column. There are many other good
> reasons to upgrade anyway.
>
> BTW the correct syntax would be
>
> CREATE UNIQUE INDEX resource_refullname
> ON resource USING btree (redtid, (upper(refullname)) text_ops);
>
> If you're going to put an opclass name, it goes outside the parens.
> (The only reason the parens are required at all is to separate the
> expression from the opclass name ...)
>
> regards, tom lane
I thought it might be version related. I had planned to upgrade soon and
this is another good motivator.
Thank you,
Margaret Gillon
From | Date | Subject | |
---|---|---|---|
Next Message | Terry Lee Tucker | 2006-04-06 18:44:57 | Re: plgpsql and transactions |
Previous Message | Wayne Schroeder | 2006-04-06 18:37:30 | The dangers of long running open transactions |