| From: | "Phoenix Kiula" <phoenix(dot)kiula(at)gmail(dot)com> |
|---|---|
| To: | Ben <bench(at)silentmedia(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:56:52 |
| Message-ID: | e373d31e0708151056m52c1fce7lb6c7f887b8b9d836@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 16/08/07, Ben <bench(at)silentmedia(dot)com> wrote:
> 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.
>
This is very useful, thanks. This would be "bytea"? Quick questions:
1. Even if it were bytea, would it work with regular SQL operators
such as regexp and LIKE?
2. Would tsearch2 work with bytea in the future as long as the stuff
in it was text?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phoenix Kiula | 2007-08-15 18:01:50 | Re: Best practice for: ERROR: invalid byte sequence for encoding "UTF8" |
| Previous Message | Leif B. Kristensen | 2007-08-15 17:53:45 | Re: pg_dump on local Windows, pg_restore on Linux? |