BUG #7505: Backslash escaping not necessary

From: ovadyaj(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #7505: Backslash escaping not necessary
Date: 2012-08-24 19:59:59
Message-ID: E1T502x-0004da-K3@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 7505
Logged by: Jeff Ovadya
Email address: ovadyaj(at)gmail(dot)com
PostgreSQL version: 9.1.4
Operating system: PostgreSQL 9.1.4, compiled by Visual C++ build 150
Description:

INSERT INTO customer VALUES ( 20, 'Mr', 'Jeff', 'Baggott', 'Midtown Street
A\\33', 'Milltown', 'MT9 8NQ', '746 3956'); results in two backslashes
instead of a single one.

Inserting the address with a single backslash succeeds in saving the
backslash with the address.

Also noticed similar issue escaping single quotes: Backslash will not work
to escape, but doubling up the quotes works.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message crispond 2012-08-25 00:56:28 BUG #7506: Windows 64 bit PGAdmin 1.14.3 plpgsql default parameter value not appearing
Previous Message Amit Kapila 2012-08-24 14:48:09 Re: Minor inheritance/check bug: Inconsistent behavior