| 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: | 3EF93DF4.3030507@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-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.
Joe
| Attachment | Content-Type | Size |
|---|---|---|
| datatype.sgml.diff | text/html | 1.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hubert Lubaczewski | 2003-06-25 06:25:39 | Re: postgres 7.3.3 problem - not talking across port |
| Previous Message | Stephen Robert Norris | 2003-06-25 06:00:23 | Re: bytea char escaping |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2003-06-25 06:45:28 | Re: allowed user/db variables |
| Previous Message | Dennis Björklund | 2003-06-25 06:05:05 | Re: Patch for psql to avoid altering the PGresult strings |