Re: [SQL] Changing character set when the damage is done

2006-12-24 Thread Michael Fuhr
On Sun, Dec 24, 2006 at 06:44:04PM +0100, Alexis Paul Bertolini wrote: > >SELECT convert(colname, 'utf8', 'latin1') FROM tablename; > > Yep, I meant the A with the tilde (the word cedilla sounded Spanish... > lol). Thanks, the "convert" function does the trick for me. If possible consider recreat

Re: [SQL] Changing character set when the damage is done

2006-12-24 Thread Alexis Paul Bertolini
Michael Fuhr wrote: Are you sure that's not a tilde (a wavy line above the A) instead of a cedilla (a hook below the A)? The UTF-8 encoding for lowercase e with grave is 0xc3 0xa8, which in ISO-8859-1 (LATIN1) or Windows-1252 is uppercase A with tilde followed by a diaeresis (an umlaut on its ow

Re: [SQL] Changing character set when the damage is done

2006-12-24 Thread Michael Fuhr
On Sun, Dec 24, 2006 at 05:05:37PM +0100, Alexis Paul Bertolini wrote: > They show up in PHP, PgAdminIII and psql. All the same. A lowercase e > with a grave accent appears as a capital A with the cedilla, followed by > an umlaut (just the umlaut, on its own). So to answer your question, > they

Re: [SQL] Changing character set when the damage is done

2006-12-24 Thread Alexis Paul Bertolini
Ragnar wrote: On lau, 2006-12-23 at 00:12 +0100, Alexis Paul Bertolini wrote: depends on whether all imports have been in the same encoding or not. SQL_ASCII basically accepts and stores the characters without interpretation, so if all imorts were done with one client_encoding, you should be