[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] Bug in UTF8-Validation Code?
From:       Mario Weilguni <mweilguni () sime ! com>
Date:       2007-03-19 12:42:35
Message-ID: 200703191342.36135.mweilguni () sime ! com
[Download RAW message or body]

Am Sonntag, 18. März 2007 12:36 schrieb Martijn van Oosterhout:
>
> It seems to me that the easiest solution would be to forbid \x?? escape
> sequences where it's greater than \x7F for UTF-8 server encodings.
> Instead introduce a \u escape for specifying the unicode character
> directly. Under the basic principle that any escape sequence still has
> to represent a single character. The result can be multiple bytes, but
> you don't have to check for consistancy anymore.

Would'nt the best solution to change the order of 
validation/convert_backslash_sequences better? First convert the sequences, 
and reject them in the validation stage?

Regards
Mario Weilguni

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org

[prev in list] [next in list] [prev in thread] [next in thread]