Re: Unique constraint or index, case insensitive, on multiple

Поиск
Список
Период
Сортировка
От MargaretGillon@chromalloy.com
Тема Re: Unique constraint or index, case insensitive, on multiple
Дата
Msg-id OF080D0C37.029F8DAD-ON88257148.0066595D-88257148.0066A042@CHROMALLOY.COM
обсуждение исходный текст
Ответ на Re: Unique constraint or index, case insensitive, on multiple fields  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general

>Tom Lane <tgl@sss.pgh.pa.us> wrote on 04/06/2006 11:33:57 AM:
> MargaretGillon@chromalloy.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

В списке pgsql-general по дате отправления:

Предыдущее
От: Wayne Schroeder
Дата:
Сообщение: The dangers of long running open transactions
Следующее
От: Terry Lee Tucker
Дата:
Сообщение: Re: plgpsql and transactions