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

On 16/08/07, Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> wrote:
> 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?

I get the following error when I try to change a column that was
hitherto "varchar(500)" to bytea--

SQL error:
ERROR: column "title" cannot be cast to type "bytea"

In statement:
ALTER TABLE "links" ALTER COLUMN "title" TYPE bytea

Any thoughts on how I can overcome this limitation?