Re: [PATCHES] bytea char escaping

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au>, Ivar <ivar(at)lumisoft(dot)ee>, pgsql-general(at)postgresql(dot)org, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [PATCHES] bytea char escaping
Date: 2003-07-18 03:45:43
Message-ID: 200307180345.h6I3jhK02041@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-patches


Patch applied. Thanks.

---------------------------------------------------------------------------

Joe Conway wrote:
> 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.
>
> Joe

[ text/html is unsupported, treating like TEXT/PLAIN ]

> Index: doc/src/sgml/datatype.sgml
> ===================================================================
> RCS file: /opt/src/cvs/pgsql-server/doc/src/sgml/datatype.sgml,v
> retrieving revision 1.119
> diff -c -r1.119 datatype.sgml
> *** doc/src/sgml/datatype.sgml 25 Jun 2003 03:50:52 -0000 1.119
> --- doc/src/sgml/datatype.sgml 25 Jun 2003 06:19:28 -0000
> ***************
> *** 1062,1069 ****
> literal in an <acronym>SQL</acronym> statement. In general, to
> escape an octet, it is converted into the three-digit octal number
> equivalent of its decimal octet value, and preceded by two
> ! backslashes. Some octet values have alternate escape sequences, as
> ! shown in <xref linkend="datatype-binary-sqlesc">.
> </para>
>
> <table id="datatype-binary-sqlesc">
> --- 1062,1070 ----
> literal in an <acronym>SQL</acronym> statement. In general, to
> escape an octet, it is converted into the three-digit octal number
> equivalent of its decimal octet value, and preceded by two
> ! backslashes. <xref linkend="datatype-binary-sqlesc"> contains the
> ! characters which must be escaped, and gives the alternate escape
> ! sequences where applicable.
> </para>
>
> <table id="datatype-binary-sqlesc">

>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Raymond 2003-07-18 03:50:40 Access 97 DB to Postgres Migration Questions
Previous Message Lauren Matheson 2003-07-18 01:04:58 Re: changing an update via rules - caught in recursion

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-07-18 03:50:11 Re: [NOVICE] connectby(... pos_of_sibling)
Previous Message Bruce Momjian 2003-07-18 03:42:58 Re: %x, %g warnings