Re: [HACKERS] UTF8 or Unicode - Mailing list pgsql-patches

From lsunley@mb.sympatico.ca
Subject Re: [HACKERS] UTF8 or Unicode
Date
Msg-id 0ICJ00A3SPGWOL@l-daemon
Whole thread Raw
List pgsql-patches
In <200502270055.j1R0te122973@candle.pha.pa.us>, on 02/26/05
   at 07:55 PM, Bruce Momjian <pgman@candle.pha.pa.us> said:

>lsunley@mb.sympatico.ca 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', 'ascii_to_mic'
>> LANGUAGE 'c' STRICT;
>>
>> CREATE CONVERSION pg_catalog.ascii_to_whatever FOR 'SQL_ASCII' TO
>> 'MULE_INTERNAL' FROM ascii_to_whatever;

>I would like to avoid bloating the system with aliases.  I think it is OK
>to have it happen with specific names but doing it for all the
>combinations is too much, and these duplicates are in the system tables,
>not in the C code.  It just doesn't seem worth it to me.

Good point, perhaps having a script generated that can be executed by the
DBA to insert any deprecated conversion routine names would be the best
route to take.

That way they would only be there if needed by the particular
installation.

--
-----------------------------------------------------------
lsunley@mb.sympatico.ca
-----------------------------------------------------------


pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #1466: #maintenace_work_mem = 16384
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] UTF8 or Unicode