Re: Best way to use indexes for partial match at - Mailing list pgsql-general

From Andrus
Subject Re: Best way to use indexes for partial match at
Date
Msg-id dktrp4$b1g$1@news.hub.org
Whole thread Raw
In response to Best way to use indexes for partial match at beginning  ("Andrus Moor" <eetasoft@online.ee>)
Responses Re: Best way to use indexes for partial match at  (Scott Marlowe <smarlowe@g2switchworks.com>)
List pgsql-general
Scott,

>> I'm searching a way to use Postgres regular index for this.
>
> Easy, do what those other databases do.  Setup your database to not use
> a locale.
>
> initdb --locale=C
>
> and you're golden.

thank you.

My language has letters in ������ with correstonding upper case letters
������

I need to prevent entering of duplicate customer names into database.
For this I created unique index on UPPER(customer_name)

I need also search for customer name in case-insensitive way. For this I use
ILIKE operator.

Those two features are working in Postgres 8.1 when I use non-C locale.
If I switch to C locale, they will not work.

My current database, Microsoft Visual Foxpro implements this functionality.

How to implement this functionality in Postgres if I switch to C locale ?

Andrus.



pgsql-general by date:

Previous
From: "Gavin M. Roy"
Date:
Subject: Kudos to the pgAdmin3 Team
Next
From: "Andrus"
Date:
Subject: Re: Best way to use indexes for partial match at beginning