Re: Patch for collation using ICU

> Palle Girgensohn wrote:
> > 
> > --On l?rdag, maj 07, 2005 23.15.29 +1000 John Hansen <john@geeknet.com.au> 
> > wrote:
> > 
> > > Btw, I had been planning to propose replacing every single one of the
> > > built in charset conversion functions with calls to ICU (thus making pg
> > > _depend_ on ICU), as this would seem like a cleaner solution than for us
> > > to maintain our own conversion tables.

I don't buy it. If current conversion tables does the right thing, why
we need to replace. Or if conversion tables are not correct, why don't
you fix it? I think the rule of character conversion will not change
frequently, especially for LATIN languages. Thus maintaining cost is
not too high.
--
Tatsuo Ishii

> > > ICU also has a fair few conversions that we do not have at present.
> 
> That is a much larger issue, similar to our shipping our own timezone
> database.  What does it buy us?
> 	
> 	o  Do we ship it in our tarball?
> 	o  Is the license compatible?
> 	o  Does it remove utils/mb conversions?
> 	o  Does it allow us to index LIKE (next high char)?
> 	o  Does it allow us to support multiple encodings in
> 	   a single database easier?
> 	o  performance?