Re: Best practice for: ERROR: invalid byte sequence for encoding "UTF8" - Mailing list pgsql-general

From Ben
Subject Re: Best practice for: ERROR: invalid byte sequence for encoding "UTF8"
Date
Msg-id Pine.LNX.4.64.0708151041450.18380@localhost.localdomain
Whole thread Raw
In response to Re: Best practice for: ERROR: invalid byte sequence for encoding "UTF8"  ("Phoenix Kiula" <phoenix.kiula@gmail.com>)
Responses Re: Best practice for: ERROR: invalid byte sequence for encoding "UTF8"
List 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.

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: pg_dump on local Windows, pg_restore on Linux?
Next
From: "Scott Marlowe"
Date:
Subject: Re: User-Friendly TimeZone List