Re: invalidly encoded strings

From: db(at)zigo(dot)dhs(dot)org
To: "Gregory Stark" <stark(at)enterprisedb(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jeff Davis" <pgsql(at)j-davis(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: invalidly encoded strings
Date: 2007-09-10 08:45:59
Message-ID: 40010.192.121.104.48.1189413959.squirrel@zigo.dhs.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

>>> I think the concern is when they use only one slash, like:
>>> E'\377\000\377'::bytea
>>> which, as I mentioned before, is not correct anyway.
>
> Wait, why would this be wrong? How would you enter the three byte bytea of
> consisting of those three bytes described above?

Either as

E'\\377\\000\\377'

or

'\377\000\377'

/Dennis

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jens-Wolfhard Schicke 2007-09-10 08:56:52 Re: Hash index todo list item
Previous Message Gregory Stark 2007-09-10 08:04:54 Re: invalidly encoded strings

Browse pgsql-patches by date

  From Date Subject
Next Message Pavan Deolasee 2007-09-10 09:57:05 Re: HOT patch - version 15
Previous Message Simon Riggs 2007-09-10 08:17:18 Re: HOT patch - version 15