From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | "Mitchell D(dot) Russell" <mitchell(dot)russell(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: v8.3 + UTF8 errors when restoring DB |
Date: | 2008-03-09 10:26:17 |
Message-ID: | 20080309102617.GA17440@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Mar 09, 2008 at 06:12:14AM -0400, Mitchell D. Russell wrote:
> Just as an update to this matter, I created another new database with
> SQL_ASCII encoding and imported the data, and it worked fine, however, I
> don't think that's the best solution because SQL_ASCII's not a good way to
> have the database encoding set, right?
SQL_ASCII means "no encoding". Everything becomes a bunch of bytes and
there's no checking whatsoever.
> I did a PG_dump of the database tonight, and went to restore it to my newly
> created database (WIN2152 encoding), which worked fine, but when I go to
> retrieve the data via my code (.NET c#), I get errors like :
Any particular reason you're using that encoding? Why not just use UTF-8?
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Gibson (DB Administrator) | 2008-03-09 13:57:51 | Re: v8.3 + UTF8 errors when restoring DB |
Previous Message | Mitchell D. Russell | 2008-03-09 10:12:14 | Re: v8.3 + UTF8 errors when restoring DB |