> >>> ICU support should make it to 8.1 I hear, which will make the
> >>> bahaviour uniform.
> >>
> >> There was some discussion about that, but my impression
> was that that
> >> wasn't going to happen.
>
> > AFAIK the result was that it would go in as an alternative,
> but not to
> > *repla
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>>> ICU support should make it to 8.1 I hear, which will make the
>>> bahaviour uniform.
>>
>> There was some discussion about that, but my impression was
>> that that wasn't going to happen.
> AFAIK the result was that it would go in as an alternat
> > ICU support should make it to 8.1 I hear, which will make the
> > bahaviour uniform.
>
> There was some discussion about that, but my impression was
> that that wasn't going to happen.
AFAIK the result was that it would go in as an alternative, but not to
*replace* what's there now.
//Magn
On Wed, Jul 20, 2005 at 08:35:33 +1000,
John Hansen <[EMAIL PROTECTED]> wrote:
>
> ICU support should make it to 8.1 I hear, which will make the bahaviour
> uniform.
There was some discussion about that, but my impression was that that
wasn't going to happen.
---(end of
Hi,
PE> PostgreSQL does not support UTF8 locales on Windows, but the character
PE> conversion should work the same on all platforms, shouldn't it?
It works pretty fine even under win32, all umlauts are coverted as
expexted, except for the "ß" (ß).
For example, "Köln" converts to "Köln", but ""Gr
Hi Tatsuo,
Am Mittwoch, 20. Juli 2005 um 01:00 schrieben Sie:
TI> conversion tables. So if german umlauts are converted fine, there's no
TI> reason the conversion for german sharp s does not work.
TI> Marcus,
TI> Can you give me the exact error message from PostgreSQL when the
TI> conversio fai
Hi,
Am Mittwoch, 20. Juli 2005 um 10:27 schrieben Sie:
TI> Problem here is the result of convert(ort using utf_8_to_iso_8859_1)
TI> is ISO-8859-1 but your database encoding is UTF-8,
Not exactly, my database is in iso_8859_1, only the opengeodb-dump is
solely available in utf-8.
The whole thing
The following bug has been logged online:
Bug reference: 1777
Logged by: nicolas
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.2
Operating system: Linux Debian
Description:Cache lookup filed
Details:
ERROR: fmgr_info: function 16556: cache lookup failed
-
I have a next problem
ERROR: fmgr_info: function 16556:
cache lookup failed
Nicolas Alberto Recab
> TI> Problem here is the result of convert(ort using utf_8_to_iso_8859_1)
> TI> is ISO-8859-1 but your database encoding is UTF-8,
>
> Not exactly, my database is in iso_8859_1, only the opengeodb-dump is
> solely available in utf-8.
> The whole thing is no problem so far, as I can convert the va
> Hi Tatsuo,
>
> Am Mittwoch, 20. Juli 2005 um 01:00 schrieben Sie:
>
> TI> conversion tables. So if german umlauts are converted fine, there's no
> TI> reason the conversion for german sharp s does not work.
>
> TI> Marcus,
>
> TI> Can you give me the exact error message from PostgreSQL when t
11 matches
Mail list logo
