Kommentare zu: PostgreSQL: TO_ASCII & UTF8

Von: Antonio Garcia

Antonio Garcia — Tue, 02 Aug 2011 10:03:08 +0000

Thank for this solution.

Von: Rodrigo Almeida

Rodrigo Almeida — Tue, 01 Feb 2011 18:01:42 +0000

Problem solved! One point for you! Thank you.

Von: emi

emi — Tue, 16 Nov 2010 11:50:09 +0000

I have the same problem that @poncho. I have tried with LATIN1, LATIN2, LATIN9 and WIN1250, but all of them fail.

This is a 7000 rows table, so looking “manually” for a bad character is not a way.

Any help on this?

Thanks in advance.

Von: Santiago Sexo

Santiago Sexo — Tue, 04 Aug 2009 05:55:37 +0000

any news coming ?

Von: loob

loob — Tue, 14 Jul 2009 08:00:11 +0000

poncho: I just change the encoding from latin1 to latin2 and it works now!

Von: poncho

poncho — Tue, 26 May 2009 18:49:01 +0000

There are characters that cannot be converted from utf to latin.
If you have only one record with such character, every query using convert_to raises an error.
Have someone found out how to work around this?

Von: eMerzh

eMerzh — Wed, 18 Mar 2009 10:06:56 +0000

oups
CREATE FUNCTION to_ascii(bytea, name)
RETURNS text STRICT AS ‘to_ascii_encname’ LANGUAGE internal;

Von: eMerzh

eMerzh — Wed, 18 Mar 2009 10:06:18 +0000

Thanks for your function …

But…

if you do select public.to_ascii(null::bytea, ‘latin1′);

Postmaster will crash!

because of the null value!

Please mark your function to strict :

CREATE FUNCTION to_ascii(bytea, name)
RETURNS STRICT text AS ‘to_ascii_encname’ LANGUAGE internal;

Von: P

Tue, 17 Mar 2009 14:26:59 +0000

Problem solved too.
You saved my life.

Thx for share!