Skip site navigation (1) Skip section navigation (2)

Re: bytea char escaping

From: Joe Conway <mail(at)joeconway(dot)com>
To: Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au>
Cc: Ivar <ivar(at)lumisoft(dot)ee>, pgsql-general(at)postgresql(dot)org,"Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: bytea char escaping
Date: 2003-06-25 06:15:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-patches
Stephen Robert Norris wrote:
> Well, no. What it says is that certain values must be escaped (but
> doesn't say which ones). Then it says there are alternate escape
> sequences for some values, which it lists.
> It doesn't say "The following table contains the characters which must
> be escaped:", which would be much clearer (and actually useful).

Attached documentation patch updates the wording for bytea input 
escaping, per complaint by Stephen Norris above.

Please apply.


Attachment: datatype.sgml.diff
Description: text/html (1.2 KB)

In response to


pgsql-patches by date

Next:From: Joe ConwayDate: 2003-06-25 06:45:28
Subject: Re: allowed user/db variables
Previous:From: Dennis BjörklundDate: 2003-06-25 06:05:05
Subject: Re: Patch for psql to avoid altering the PGresult strings

pgsql-general by date

Next:From: Hubert LubaczewskiDate: 2003-06-25 06:25:39
Subject: Re: postgres 7.3.3 problem - not talking across port
Previous:From: Stephen Robert NorrisDate: 2003-06-25 06:00:23
Subject: Re: bytea char escaping

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group