Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id F0AA2B5DC19 for ; Fri, 4 Nov 2011 13:05:30 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 62191-02 for ; Fri, 4 Nov 2011 16:05:24 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from nm12.bullet.mail.ac4.yahoo.com (nm12.bullet.mail.ac4.yahoo.com [98.139.52.209]) by mail.postgresql.org (Postfix) with SMTP id D0749B5DC2D for ; Fri, 4 Nov 2011 13:05:23 -0300 (ADT) Received: from [98.139.52.192] by nm12.bullet.mail.ac4.yahoo.com with NNFMP; 04 Nov 2011 16:05:22 -0000 Received: from [98.139.52.136] by tm5.bullet.mail.ac4.yahoo.com with NNFMP; 04 Nov 2011 16:05:22 -0000 Received: from [127.0.0.1] by omp1019.mail.ac4.yahoo.com with NNFMP; 04 Nov 2011 16:05:22 -0000 X-Yahoo-Newman-Id: 791911.14312.bm@omp1019.mail.ac4.yahoo.com Received: (qmail 91221 invoked from network); 4 Nov 2011 16:05:22 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:References:Mime-Version:In-Reply-To:X-Apple-Yahoo-Original-Message-Folder:Content-Type:Content-Transfer-Encoding:Message-Id:Cc:X-Mailer:From:X-Apple-Yahoo-Replied-Msgid:Subject:Date:To; b=K+1DLPSrOevnAsF45TewdjbqkKmlqwYNbVCmMvKbIM3AHiB5dfKH2SIw2emkPxof5b6sb+ykmdr/3OeQyBPT44fRlxssHKbzIxyu3VNEZXcgUg6M+FiuiCCLM1dYXhO7plKsjOvydWg5xxevf8WcnUZ4lgIl1ZbbvA1UqjOdkig= ; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1320422722; bh=/4XiuPVlEC6APW1jM2gOA82P8dw15ENBdl7qFzxsm9I=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:References:Mime-Version:In-Reply-To:X-Apple-Yahoo-Original-Message-Folder:Content-Type:Content-Transfer-Encoding:Message-Id:Cc:X-Mailer:From:X-Apple-Yahoo-Replied-Msgid:Subject:Date:To; b=UsqtvSADGZvuasmcZACwSO+XyLHK057/J1PZc0K4lH4PLsCeSuba5ki1go1LZbnRt93jAJHjKMC/vlpuZP0M2+DonxvC/UZv+afX3mLXgQskgK63r7OS5S575/ZQh7XbCPio+9XCKeYh3c5IZ2SHfk+P03yqGRHWyHMq1xMZXog= X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: cwqM.XsVM1k8SBnqx.stTV5zJebmQlxBoutAdAK7.Gy4E.R 08lBGW7wDqwvTLg1.f33sfvW0WGytdOPphmjrFhpBT9oPveo4rzyaLZDY0CF djp9pcJfmZjjADANo4PlNS2gxd3hm7pk0l7LwZYu6vvna51fJI3bofAhdE3n Lss.fs1E0lDJz_j7zauQarLsSuujVRgaPRlMtcf.jDtuQ2CvqqohD_qxJ9CG s9PESJLbgCmtqD8Yd9Z.38RvTp2PF8311r1ewDkQ1yIDGtsUWBL8sDh2wvkE gvj732WLijV8oTzG0zPr9oCW9r3ieDsjAYUwbn4KU1Os1OLJkxAZtvu8APmF JeG.a4Vh2vXE4RKgnJEvl1aJek7O2GFQbGc09mPvpSoKzps4FR34PuTi1.0Y ieCPq8Q-- X-Yahoo-SMTP: mpGJl6eswBD2IBufoVEg0Pa8gg-- Received: from [192.12.17.103] (polobo@24.93.23.188 with xymcookie) by smtp112-mob.biz.mail.ac4.yahoo.com with SMTP; 04 Nov 2011 09:05:22 -0700 PDT References: <201111040738.29303.johnf@jfcomputer.com> <201111040826.16177.johnf@jfcomputer.com> Mime-Version: 1.0 (iPad Mail 8J2) In-Reply-To: <201111040826.16177.johnf@jfcomputer.com> X-Apple-Yahoo-Original-Message-Folder: Inbox Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <5B6EF5E5-F941-4D32-AF03-6BBCD6E83769@yahoo.com> Cc: "pgsql-sql@postgresql.org" X-Mailer: iPad Mail (8J2) From: David Johnston X-Apple-Yahoo-Replied-Msgid: 1_481055_APOkiGIAAEEhTrQElQjLiRcFMh4 Subject: Re: the use of $$string$$ Date: Fri, 4 Nov 2011 12:05:19 -0400 To: John Fabiani X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-3.1 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.201 X-Spam-Level: X-Archive-Number: 201111/17 X-Sequence-Number: 35990 On Nov 4, 2011, at 11:26, John Fabiani wrote: > On Friday, November 04, 2011 07:38:29 am John Fabiani wrote: >> Hi, >> I just discovered that I can use $$string$$ to account for the problem of= >> single quotes in the string (or other strange char's). However, I notice= d >> that the table field contained E'string'. I actually tried to find info o= n >> this but I did not find anything. >>=20 >> Could someone explain what it means or better provide a web link for me t= o >> discover the info. >>=20 >> Thanks in advance, >> Johnf >=20 >=20 > Thank you both for the quick replies and the links. =20 >=20 > What I still do not understand (I'm a little slow) is the fact that pgadmi= n3=20 > showed the data as E'string'. So I'm wondering if the data is now differe= nt=20 > in the sense that I need use the 'E' in the field. >=20 > For example I have the last name of O'Reilly > the field lname now appears to contain E'O'Reilly' >=20 > So will the normal select statements work; >=20 > Select * from table where lname =3D 'O'' Reilly' > Select * from table where lname like 'O%' >=20 > or will I need to know the data contains the "E" and add the 'E' to the s= ql=20 > statements? >=20 > Thanks > Johnf >=20 >=20 Try it and see. If, indeed, the E is part of the data you should fix your process. Done cor= rectly there should be no difference in the end result regardless of how you= choose to identify your strings. Don't use pgadmin3 myself so I don't know if what you are looking at would i= nclude the E. If it is outputting DDL (I.e., INSERT statements) it might bu= t simple SELECT results should not. David J.=