From ramang@smartdatainc.com Mon Mar  15 10:42:06 2004
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 59F85D1B91C
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 15 Mar 2004 10:42:06 +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 55599-02
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 15 Mar 2004 06:42:06 -0400 (AST)
Received: from smartdatainc.com (unknown [202.164.35.114])
	by svr1.postgresql.org (Postfix) with ESMTP id 9F46CD1B80B
	for <pgsql-sql@postgresql.org>; Mon, 15 Mar 2004 06:42:01 -0400 (AST)
Received: from raman ([192.168.199.212]) by smartdatainc.com
 ([192.168.199.92])
	with SMTP (MDaemon.PRO.v6.5.2.R)
	for <pgsql-sql@postgresql.org>; Mon, 15 Mar 2004 16:10:30 +0530
Message-ID: <00ec01c40a79$7ec4be00$d4c7a8c0@raman>
From: "Raman" <ramang@smartdatainc.com>
To: <pgsql-sql@postgresql.org>
Subject: Invalid Characters
Date: Mon, 15 Mar 2004 16:07:16 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00E5_01C40AA7.95BCA180"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-MDRemoteIP: 192.168.199.212
X-Return-Path: ramang@smartdatainc.com
X-MDaemon-Deliver-To: pgsql-sql@postgresql.org
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=BAYES_44,
	HTML_MESSAGE
X-Spam-Level: 
X-Archive-Number: 200403/154
X-Sequence-Number: 17253

This is a multi-part message in MIME format.

------=_NextPart_000_00E5_01C40AA7.95BCA180
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,

I have imported some data from csv files in my DB. Now that data has some i=
nvalid characters stored in it.
so I get this exception:

Exception in ChannelDAO Invalid character data was found.  This is most lik=
ely caused by stored data containing characters that are invalid for the ch=
aracter set
 the database was created in.  The most common example of this is storing 8=
bit 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
------=_NextPart_000_00E5_01C40AA7.95BCA180
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I have imported some data from csv files i=
n my DB.=20
Now that data has some invalid characters stored in it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>so I get this exception:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Exception in ChannelDAO Invalid character =
data was=20
found.&nbsp; This is most likely caused by stored data containing character=
s=20
that are invalid for the character set<BR>&nbsp;the database was created=20
in.&nbsp; The most common example of this is storing 8bit data in a SQL_ASC=
II=20
database.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Now, I tried using to_ascii() fn in my sel=
ect query=20
but it didn't work. Cn you please suggest any solution so that invalid=20
characters should not come to my webpage while displaying.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><STRONG>Raman=20
Garg</STRONG></FONT></DIV></BODY></HTML>

------=_NextPart_000_00E5_01C40AA7.95BCA180--




From paul@tmsl.demon.co.uk Mon Mar  15 11:42:25 2004
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 <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	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 <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	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 <pgsql-sql@postgresql.org>; 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 <paul@tmsl.demon.co.uk>
To: Raman <ramang@smartdatainc.com>
Cc: "pgsql-sql @ postgresql . org" <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   |
+------------------------------+---------------------------------------------+