Tom, I will try to add "set client_encoding = sql_ascii;" and pray :)
Cheers, Dion > -----Original Message----- > From: Tom Lane [mailto:[EMAIL PROTECTED] > Sent: Monday, April 19, 2004 9:21 PM > To: Dion Almaer > Cc: [EMAIL PROTECTED]; 'Lloyd Benson'; Eric Preston > Subject: Re: [ADMIN] Going from a DB using SQL_ASCII to UNICODE > > "Dion Almaer" <[EMAIL PROTECTED]> writes: > > When we try to import the data from a SQL_ASCII dumped db, into the > > new UNICODE db, everything freaks out. > > I'm no expert on this stuff, but I think what you need to do is add > > set client_encoding = sql_ascii; > > to the top of the dump file. (As of fairly recently, pg_dump > will automatically add such a SET, but I'm pretty sure 7.4.2 won't.) > > If that doesn't help, then what you have is actually not > valid UTF-8 data, and what you'll have to do is figure out > what encoding it's in and specify that instead. If it's in a > mishmash of different encodings, you're in for some pain :-( > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
