Skip site navigation (1) Skip section navigation (2)

Re: Invalid Characters

From: Paul Thomas <paul(at)tmsl(dot)demon(dot)co(dot)uk>
To: Raman <ramang(at)smartdatainc(dot)com>
Cc: "pgsql-sql (at) postgresql (dot) org" <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Invalid Characters
Date: 2004-03-15 11:42:23
Message-ID: 20040315114223.A412@bacon (view raw or flat)
Thread:
Lists: pgsql-sql
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   |
+------------------------------+---------------------------------------------+

In response to

pgsql-sql by date

Next:From: John DeSoiDate: 2004-03-15 13:28:50
Subject: Re: Object-relational features
Previous:From: RamanDate: 2004-03-15 10:37:16
Subject: Invalid Characters

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group