From: | David Wheeler <david(at)wheeler(dot)net> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 7.4 Wishlist |
Date: | 2002-12-01 04:24:17 |
Message-ID: | C1805CA7-04E4-11D7-8D38-0003931A964A@wheeler.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-general pgsql-hackers |
On Saturday, November 30, 2002, at 07:24 PM, Joe Conway wrote:
> That is one thing I'd like to take a look at. I think the problem is
> that certain byte-sequence/multibyte-encoding combinations are
> illegal, so it's not as simple an issue as it might first appear.
My understanding is that the nul character is legal in a byte sequence,
but if it's not properly escaped, it'll be parsed as the end of the
statement. Unfortunately, I think that it's a very tough problem to
solve.
David
--
David Wheeler AIM: dwTheory
david(at)wheeler(dot)net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory(at)jabber(dot)org
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-12-01 04:53:33 | Re: Hard-coded PUBLIC in pg_dump |
Previous Message | Nicolai Tufar | 2002-12-01 04:20:50 | Re: Segmentation fault while COPY in 7.3 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-12-01 04:39:42 | Re: returning CHAR from C function |
Previous Message | Nicolai Tufar | 2002-12-01 04:20:50 | Re: Segmentation fault while COPY in 7.3 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-12-01 04:28:47 | Re: Wishlist for 7.4: Plan stability |
Previous Message | Nicolai Tufar | 2002-12-01 04:20:50 | Re: Segmentation fault while COPY in 7.3 |