Re: Best practice for: ERROR: invalid byte sequence for encoding "UTF8"

From: Ben <bench(at)silentmedia(dot)com>
To: Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Ivan Zolotukhin <ivan(dot)zolotukhin(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Best practice for: ERROR: invalid byte sequence for encoding "UTF8"
Date: 2007-08-15 17:43:59
Message-ID: Pine.LNX.4.64.0708151041450.18380@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 16 Aug 2007, Phoenix Kiula wrote:

> I am not advocating what others should do. But I know what I need my
> DB to do. If I want it to store data that does not match puritanical
> standards of textual storage, then it should allow me to...

It does allow that: store it as a BLOB, and then treat it as text in your
app.

Me personally, if I expect something to be text, I expect it to be valid
text.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2007-08-15 17:44:38 Re: User-Friendly TimeZone List
Previous Message Scott Marlowe 2007-08-15 17:42:28 Re: pg_dump on local Windows, pg_restore on Linux?