Re: Invalid Unicode Character Sequence found

From: "Bulatovic Natasa" <n(dot)bulatovic(at)zim(dot)mpg(dot)de>
To: "'Markus Bertheau'" <twanger(at)bluetwanger(dot)de>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Invalid Unicode Character Sequence found
Date: 2004-03-29 07:33:13
Message-ID: 002b01c41560$19f0c630$e402b782@ipp.ipp.mpg.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Yes, indeed very strange.
However, it is certainly fixed, because I also tried more advanced
version of postgres and this bug was not in there.

Regards
Natasa

> -----Original Message-----
> From: Markus Bertheau [mailto:twanger(at)bluetwanger(dot)de]
> Sent: Saturday, March 27, 2004 11:02 AM
> To: Tom Lane
> Cc: Bulatovic Natasa; pgsql-sql(at)postgresql(dot)org
> Subject: Re: [SQL] Invalid Unicode Character Sequence found
>
>
> В Птн, 26.03.2004, в 22:43, Tom Lane пишет:
> > "Bulatovic Natasa" <n(dot)bulatovic(at)zim(dot)mpg(dot)de> writes:
> > > select id, title from docs where title like 'z%'; or
> > > select id, title from docs where title like 'Z%';
> > > It reports the following error:
> > > ERROR: Invalid UNICODE character sequence found (0xc000)
> >
> > This is fixed in 7.3.6.
>
> I remember to have stumbled over this bug, too. I poked
> around in the code a bit but found nothing that hinted to
> cause of the bug. So I wonder what the cause of this bug was?
>
> --
> Markus Bertheau <twanger(at)bluetwanger(dot)de>
>
>

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Jon Poulton 2004-03-29 17:12:46 Question on pgsql trigger
Previous Message Tsoloane Moahloli 2004-03-29 07:30:46 Re: date_part stored procs