|
Home > Archive > PostgreSQL Discussion > April 2006 > Re: Unique constraint or index, case insensitive, on multiple
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Unique constraint or index, case insensitive, on multiple
|
|
| MargaretGillon@chromalloy.com 2006-04-06, 8:25 pm |
| >Tom Lane <tgl@sss.pgh.pa.us> wrote on 04/06/2006 11:33:57 AM:
> MargaretGillon@chrom
alloy.com writes:
>
> 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
|
|
|
|
|