Bruce Momjian writes:
>> The correct encoding name is "UTF-8".
> True, but Peter says the ANSI standard calls it UTF8 so that's what I
> used.
What SQL99 actually says is
- UTF8 specifies the name of a character repertoire that consists
of every character represented by Th
Markus Bertheau ? wrote:
> ? ???, 26/02/2005 ? 15:50 -0500, Bruce Momjian ?:
>
> > Other than that the other conversion files were already named fine, e.g.
> > ascii_to_utf_8 (no UNICODE), however it is utf_8 and not utf8. I am
> > unsure how to handle these.
>
> General remark about the spe
Ð ÐÐÑ, 26/02/2005 Ð 15:50 -0500, Bruce Momjian ÐÐÑÐÑ:
> Other than that the other conversion files were already named fine, e.g.
> ascii_to_utf_8 (no UNICODE), however it is utf_8 and not utf8. I am
> unsure how to handle these.
General remark about the spelling of this encoding:
The correct en
Ignore previous e-mail...
Missed the patch to the makefile
Sorry about that
--
---
[EMAIL PROTECTED]
---
---(end of broadcast)---
TIP
In <[EMAIL PROTECTED]>, on 02/26/05
at 11:09 PM, Bruce Momjian said:
>Here is an updated version that handles all cases. It does rename the
>routine names so the primary encoding name is used for the routine names.
>This will be documented in the release notes if anyone actually uses
>tho
The routines that do the conversion could have alternate names specified
in the conversion_create.sql. There is not reason that I can see why you
cannot have two function names pointing to the same routine.
like
CREATE OR REPLACE FUNCTION ascii_to_mic (INTEGER, INTEGER, CSTRING,
CSTRING, INTEGER)
Further to my earlier e-mail, there would have to be two lines added to
conversion_create.sql for each alternate function name
Like:
CREATE OR REPLACE FUNCTION ascii_to_whatever (INTEGER, INTEGER, CSTRING,
CSTRING, INTEGER) RETURNS VOID AS '$libdir/ascmic', 'ascii_to_mic'
LANGUAGE 'c' STRICT;
CR
[EMAIL PROTECTED] wrote:
> Further to my earlier e-mail, there would have to be two lines added to
> conversion_create.sql for each alternate function name
>
> Like:
>
> CREATE OR REPLACE FUNCTION ascii_to_whatever (INTEGER, INTEGER, CSTRING,
> CSTRING, INTEGER) RETURNS VOID AS '$libdir/ascmic',
In <[EMAIL PROTECTED]>, on 02/26/05
at 07:55 PM, Bruce Momjian said:
>[EMAIL PROTECTED] wrote:
>> Further to my earlier e-mail, there would have to be two lines added to
>> conversion_create.sql for each alternate function name
>>
>> Like:
>>
>> CREATE OR REPLACE FUNCTION ascii_to_whatever
[EMAIL PROTECTED] wrote:
> In <[EMAIL PROTECTED]>, on 02/26/05
>at 07:55 PM, Bruce Momjian said:
>
> >[EMAIL PROTECTED] wrote:
> >> Further to my earlier e-mail, there would have to be two lines added to
> >> conversion_create.sql for each alternate function name
> >>
> >> Like:
> >>
> >>
10 matches
Mail list logo
