On Wed, Mar 23, 2011 at 08:05, Kasia Tuszynska <ktuszynska@esri.com> wrote:
> I was wondering if this was considered a bug, and if so what were the plans
> to fix it: http://archives.postgresql.org/pgsql-bugs/2005-08/msg00211.php
The wave dash issue is not postgres-specific; some other converter just
replace it with '?'. Instead, postgres throws an error.
I guess there is no possibility to support ambiguous character mappings
in the default conversions, but you can define more relaxed conversion
procedures for your purpose.
BTW, we cannot use non-default conversion procedures from SQL commands,
right? If it were allowed, we can use some "relaxed" conversions
on the initial loading, like this:
=# SET character_conversion TO utf8_to_eucjp_relaxed;
=# COPY tbl FROM '/file_with_wave_dashes.utf8.tsv';
=# RESET character_conversion;
Another idea is to allow to create new encoding names and define
the above conversion procs as the default:
=# CREATE ENCODING eucjp_relaxed;
=# CREATE DEFAULT CONVERSION xxx FOR utf8 TO eucjp_relaxed
FROM utf8_to_eucjp_relaxed;
I think overhaul of conversion support is a TODO item.
--
Itagaki Takahiro
