Received: from megazone.bigpanda.com ([63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fB35Nbm57499 for ; Mon, 3 Dec 2001 00:23:37 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 0E21DD5E6; Sun, 2 Dec 2001 21:23:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 03D445BEA; Sun, 2 Dec 2001 21:23:41 -0800 (PST) Date: Sun, 2 Dec 2001 21:23:41 -0800 (PST) From: Stephan Szabo To: postgresql Cc: Megalex , Subject: Re: problems with single quotes.. In-Reply-To: <200112030308.fB338em54420@postgresql.org> Message-ID: <20011202212229.C86964-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200112/16 X-Sequence-Number: 5839 On Sun, 2 Dec 2001, postgresql wrote: > but this is exactally correct behavior.....you can use either two single quotes to > escape the quote or the backslash so..... > > ' '' \\ '' ' > singlequote to start the sequence(string) > two singlequotes to insert an escape then a singlequote (yields a single quote) > a backslash to escape the following backslash (yields a single backslash) > two singlequotes to insert an escape then a singlequote (yields a single quote) > then ended by a single quote > > this is acting correctly..... Yes. I'm assuming that '\' was what he wanted out, so I gave the sequence that worked for me. He said he'd tried escaping the backslash and didn't have it work, but I'm not sure what he meant by that.