From: John Fabiani <johnf@jfcomputer.com>
Organization: J.F. Computer Solutions
To: pgsql-sql@postgresql.org
Subject: Re: the use of $$string$$
Date: Fri, 4 Nov 2011 08:26:16 -0700
User-Agent: KMail/1.13.5 (Linux/2.6.34.10-0.2-desktop; KDE/4.4.4; i686; ; )
References: <201111040738.29303.johnf@jfcomputer.com>
In-Reply-To: <201111040738.29303.johnf@jfcomputer.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201111040826.16177.johnf@jfcomputer.com>

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 noticed
> that the table field contained E'string'.  I actually tried to find info on
> this but I did not find anything.
> 
> Could someone explain what it means or better provide a web link for me to
> discover the info.
> 
> Thanks in advance,
> Johnf


Thank you both for the quick replies and the links.  

What I still do not understand (I'm a little slow) is the fact that pgadmin3 
showed the data as E'string'.  So I'm wondering if the data is now different 
in the sense that I need use the 'E' in the field.

For example I have the last name of O'Reilly
the field lname now appears to contain E'O'Reilly'

So will the normal select statements work;

Select * from table where lname = 'O'' Reilly'
Select * from table where lname like 'O%'

or will I need to know the data contains the "E"  and add the 'E' to the sql 
statements?

Thanks
Johnf