Re: unicode upper/lower functions

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: unicode upper/lower functions

Bruce Momjian-2

I think we have decided to use the ICU library to implement multiple locales.

---------------------------------------------------------------------------

John Hansen wrote:

> Hi list,
>
>
> Attached for your perusal, unicode versions of upper/lower, that work
> independent of locale except for the following languages:
>
> Turkish, Azeri, and Lithuanian.
> There are 15 locale specific cases in total not covered.
>
>
> --
> John Hansen <[hidden email]>
> GeekNET

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  [hidden email]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match
Reply | Threaded
Open this post in threaded view
|

Re: unicode upper/lower functions

John Hansen
Yes,

Thank you! :)

.. John

> -----Original Message-----
> From: Bruce Momjian [mailto:[hidden email]]
> Sent: Tuesday, June 07, 2005 10:07 AM
> To: John Hansen
> Cc: [hidden email]
> Subject: Re: [HACKERS] unicode upper/lower functions
>
>
> I think we have decided to use the ICU library to implement
> multiple locales.
>
> --------------------------------------------------------------
> -------------
>
> John Hansen wrote:
> > Hi list,
> >
> >
> > Attached for your perusal, unicode versions of upper/lower,
> that work
> > independent of locale except for the following languages:
> >
> > Turkish, Azeri, and Lithuanian.
> > There are 15 locale specific cases in total not covered.
> >
> >
> > --
> > John Hansen <[hidden email]>
> > GeekNET
>
> [ Attachment, skipping... ]
>
> >
> > ---------------------------(end of
> > broadcast)---------------------------
> > TIP 7: don't forget to increase your free space map settings
>
> --
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   [hidden email]               |  (610) 359-1001
>   +  If your life is a hard drive,     |  13 Roberts Road
>   +  Christ can be your backup.        |  Newtown Square,
> Pennsylvania 19073
>
>

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq
Reply | Threaded
Open this post in threaded view
|

Re: unicode upper/lower functions

John Hansen
In reply to this post by Bruce Momjian-2
... Except,.. It was never decided if the 'C' locale optimisations was
going to be removed if/when implementing ICU.

Tho I think the  conclusion was a postgresql.conf parameter to
enable/disable the optimisations.
Either way, this code is now obsolete.

... John

> -----Original Message-----
> From: Bruce Momjian [mailto:[hidden email]]
> Sent: Tuesday, June 07, 2005 10:07 AM
> To: John Hansen
> Cc: [hidden email]
> Subject: Re: [HACKERS] unicode upper/lower functions
>
>
> I think we have decided to use the ICU library to implement
> multiple locales.
>
> --------------------------------------------------------------
> -------------
>
> John Hansen wrote:
> > Hi list,
> >
> >
> > Attached for your perusal, unicode versions of upper/lower,
> that work
> > independent of locale except for the following languages:
> >
> > Turkish, Azeri, and Lithuanian.
> > There are 15 locale specific cases in total not covered.
> >
> >
> > --
> > John Hansen <[hidden email]>
> > GeekNET
>
> [ Attachment, skipping... ]
>
> >
> > ---------------------------(end of
> > broadcast)---------------------------
> > TIP 7: don't forget to increase your free space map settings
>
> --
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   [hidden email]               |  (610) 359-1001
>   +  If your life is a hard drive,     |  13 Roberts Road
>   +  Christ can be your backup.        |  Newtown Square,
> Pennsylvania 19073
>
>

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to [hidden email] so that your
      message can get through to the mailing list cleanly
Reply | Threaded
Open this post in threaded view
|

Re: unicode upper/lower functions

Bruce Momjian-2
John Hansen wrote:
> ... Except,.. It was never decided if the 'C' locale optimisations was
> going to be removed if/when implementing ICU.

Uh, why would we remove it?  Oh, meaning if the locale is C we bypass
locale lookups?  I think we will have to see what performance we have
with things.

> Tho I think the  conclusion was a postgresql.conf parameter to
> enable/disable the optimisations.
> Either way, this code is now obsolete.

Thanks.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  [hidden email]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to [hidden email])
Reply | Threaded
Open this post in threaded view
|

Re: unicode upper/lower functions

John Hansen
In reply to this post by Bruce Momjian-2
Bruce Momjian wrote:
> John Hansen wrote:
> > ... Except,.. It was never decided if the 'C' locale
> optimisations was
> > going to be removed if/when implementing ICU.
>
> Uh, why would we remove it?  Oh, meaning if the locale is C
> we bypass locale lookups?  I think we will have to see what
> performance we have with things.

Uhh, not quite: If locale is 'C' the current assumption is 7-bit ASCII
for upper/lower/initcap.
ICU is capable of properky doing upper/lower/initcap except for the
cases described in this (obsolete) patch.

>
> > Tho I think the  conclusion was a postgresql.conf parameter to
> > enable/disable the optimisations.
> > Either way, this code is now obsolete.
>
> Thanks.
>
> --
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   [hidden email]               |  (610) 359-1001
>   +  If your life is a hard drive,     |  13 Roberts Road
>   +  Christ can be your backup.        |  Newtown Square,
> Pennsylvania 19073
>
>

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq