X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 77190D1C9E1 for ; Mon, 15 Mar 2004 11:42:25 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 77295-01 for ; Mon, 15 Mar 2004 07:42:26 -0400 (AST) Received: from anchor-post-35.mail.demon.net (anchor-post-35.mail.demon.net [194.217.242.85]) by svr1.postgresql.org (Postfix) with ESMTP id 953CED1C952 for ; Mon, 15 Mar 2004 07:42:23 -0400 (AST) Received: from tmsl-adsl.demon.co.uk ([80.177.114.181] helo=bacon.tmsl.demon.co.uk) by anchor-post-35.mail.demon.net with esmtp (Exim 3.35 #1) id 1B2qUD-0000ZV-0Z; Mon, 15 Mar 2004 11:42:26 +0000 Date: Mon, 15 Mar 2004 11:42:23 +0000 From: Paul Thomas To: Raman Cc: "pgsql-sql @ postgresql . org" Subject: Re: Invalid Characters Message-ID: <20040315114223.A412@bacon> References: <00ec01c40a79$7ec4be00$d4c7a8c0@raman> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-1 In-Reply-To: <00ec01c40a79$7ec4be00$d4c7a8c0@raman>; from ramang@smartdatainc.com on Mon, Mar 15, 2004 at 10:37:16 +0000 X-Mailer: Balsa 1.2.3 Lines: 36 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/155 X-Sequence-Number: 17254 On 15/03/2004 10:37 Raman wrote: > Hi All, > > I have imported some data from csv files in my DB. Now that data has some > invalid characters stored in it. > so I get this exception: > > Exception in ChannelDAO Invalid character data was found. This is most > likely caused by stored data containing characters that are invalid for > the character set > the database was created in. The most common example of this is storing > 8bit data in a SQL_ASCII database. > > > Now, I tried using to_ascii() fn in my select query but it didn't work. > Cn you please suggest any solution so that invalid characters should not > come to my webpage while displaying. > > Regards > Raman Garg > Use UNICODE as the db encoding. You'll have to drop and re-create the db though. HTH -- Paul Thomas +------------------------------+---------------------------------------------+ | Thomas Micro Systems Limited | Software Solutions for Business | | Computer Consultants | http://www.thomas-micro-systems-ltd.co.uk | +------------------------------+---------------------------------------------+