Date: Sat, 7 Dec 2002 16:19:48 -0500
From: Joel Burton <joel@joelburton.com>
To: Pedro Igor <pedroigor@aip.com.br>
Cc: pgsql-sql@postgresql.org
Subject: Re: Accent-insensitive
Message-ID: <20021207211948.GA5760@temp.joelburton.com>
References: <002401c29d2b$a6e168a0$0b00010a@aip.com.br>
	<007401c29d66$b1374690$3c8addd5@cednetwork.net>
	<20021206221732.GA22607@temp.joelburton.com>
	<002201c29e3c$f2e2c750$0200a8c0@micro02>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <002201c29e3c$f2e2c750$0200a8c0@micro02>
User-Agent: Mutt/1.3.25i

On Sat, Dec 07, 2002 at 07:06:45PM -0300, Pedro Igor wrote:
> Thanks, you know if some possible release would have some internal to deal
> with this ?
> 
> Abraços
> Pedro Igor
> >
> > CREATE FUNCTION lower_ascii (text) RETURNS text AS '
> >   BEGIN
> >     RETURN lower(to_ascii($1));
> >   END
> > ' language 'plpgsql';
> >
> > CREATE INDEX table_lower_ascii ON table(lower_ascii(field));

Pedro --

Please keep conversations on the list -- other people may know things I
don't (actually, they certainly will!), and it allows other people to
follow the conversation.

As for this being internal, I have no idea -- you could submit it as a
suggestion.

Given how easy it is to implement in plpgsql, I suspect this kind of thing will
stay out of the internals. Keep in mind that if you define this function
in your template1 database, you can have it created automatically in all
new databases you create, so it's one less thing to worry about.

HTH.

-- 

Joel BURTON  |  joel@joelburton.com  |  joelburton.com  |  aim: wjoelburton
Independent Knowledge Management Consultant