On Thursday 12 June 2008, David Giragosian wrote:
> The same is true of mysql_real_escape_string() in PHP. You escape
> special characters upon update or insertion, but upon viewing the data
> in the DB or retrieving it programmatically, the data simply appear as
> it was originally before use of
On 6/12/08, Tim Johnson <[EMAIL PROTECTED]> wrote:
> On Thursday 12 June 2008, Warren Young wrote:
> > Tim Johnson wrote:
> > > Not sure what you mean by "directly usable".
> >
> > I mean "directly usable". :)
> >
> > > If I do an insert statement with a backslash, for example:
> > > "headlin
On Thursday 12 June 2008, Warren Young wrote:
> Tim Johnson wrote:
> > Not sure what you mean by "directly usable".
>
> I mean "directly usable". :)
>
> > If I do an insert statement with a backslash, for example:
> > "headline\one", I will retrieve "headline\\one", and that will
> > need t
Tim Johnson wrote:
Not sure what you mean by "directly usable".
I mean "directly usable". :)
If I do an insert statement with a backslash, for example:
"headline\one", I will retrieve "headline\\one", and that will
need to be unescaped, because it is not a true representation
of wha
On Thursday 12 June 2008, Warren Young wrote:
> Tim Johnson wrote:
> > I can not locate a C api function to _unescape_ strings.
>
> Why do you believe you need one?
>
> You need to escape strings when building SQL query strings to avoid
> problems with quote characters, which are special in SQL. W
Tim Johnson wrote:
I can not locate a C api function to _unescape_ strings.
Why do you believe you need one?
You need to escape strings when building SQL query strings to avoid
problems with quote characters, which are special in SQL. When MySQL
returns the queried data to your program, i
