Re: Best way to use indexes for partial match at

From: "Andrus" <eetasoft(at)online(dot)ee>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Best way to use indexes for partial match at
Date: 2005-11-09 21:30:47
Message-ID: dktrp4$b1g$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-11-09 21:36:37 Re: Foreign key reference causes invalid DELETE trigger calls
Previous Message Dean Gibson (DB Administrator) 2005-11-09 21:23:44 Re: Best way to use indexes for partial match at beginning