Re: UNICODE/UTF-8 on win32

Roland Volkmann <[email protected]>
Newsgroups gmane.comp.db.postgresql.devel.win32
Message-ID <[email protected]>
Hello,

Tom Lane schrieb am 31.12.2004 20:21:
> "Magnus Hagander" <[email protected]> writes:
> 
>>We know it's broken and won't be fixed for 8.0.
> 
> 
>>If we just #ifndef WIN32 the definitions in utils/mb/encnames.c it won't
>>be possible to select that encoding, right? Will that have any other
>>unwanted effects (such as breaking client encodings)? If not, I suggest
>>this is done.
> 
> 
> I believe the subscripts in those arrays have to match the encoding
> enum type, so you can't just ifdef out individual entries.
> 
> 
>>(Or perhaps something can be done in pg_valid_server_encoding?)
> 
> 
> Making the valid_server_encoding function reject it might work.
> Tatsuo-san would know for sure.
> 
> Should we also reject it as a client encoding, or does that work OK?

what ever you will decide to do, please don't reject UTF-8 as a valid 
client encoding. This would break existing applications in our company, 
and I'm sure, not only there.


With best regards,

Roland.


---------------------------(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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.