| From: | John Fabiani <johnf(at)jfcomputer(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: the use of $$string$$ |
| Date: | 2011-11-04 15:26:16 |
| Message-ID: | 201111040826.16177.johnf@jfcomputer.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2011-11-04 16:05:19 | Re: the use of $$string$$ |
| Previous Message | Tom Lane | 2011-11-04 14:57:24 | Re: the use of $$string$$ |