Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #13816 > unrolled thread

function for preserving special characters?

Back to article view | Back to comp.lang.php

Contents

  function for preserving special characters? richard <noreply@example.com> - 2014-06-13 00:57 -0400
    Re: function for preserving special characters? Tim Streater <timstreater@greenbee.net> - 2014-06-13 10:03 +0100
      Re: function for preserving special characters? Christoph Michael Becker <cmbecker69@arcor.de> - 2014-06-13 15:32 +0200
        Re: function for preserving special characters? Tim Streater <timstreater@greenbee.net> - 2014-06-13 14:42 +0100
          Re: function for preserving special characters? Christoph Michael Becker <cmbecker69@arcor.de> - 2014-06-13 16:26 +0200
            Re: function for preserving special characters? Tim Streater <timstreater@greenbee.net> - 2014-06-13 18:23 +0100
    Re: function for preserving special characters? Doug Miller <doug_at_milmac_dot_com@example.com> - 2014-06-13 10:39 +0000
      Re: function for preserving special characters? Paul Herber <paul@pherber.com> - 2014-06-13 12:37 +0100
        Re: function for preserving special characters? Doug Miller <doug_at_milmac_dot_com@example.com> - 2014-06-13 12:59 +0000
        Re: function for preserving special characters? richard <noreply@example.com> - 2014-06-13 14:45 -0400
    solved  (was: function for preserving special characters?) richard <noreply@example.com> - 2014-06-13 09:57 -0400
      Re: solved Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-13 10:14 -0400
        Re: solved richard <noreply@example.com> - 2014-06-13 14:43 -0400
          Re: solved Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-13 15:01 -0400
            Re: solved richard <noreply@example.com> - 2014-06-13 15:44 -0400
              Re: solved Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-13 16:09 -0400
              Re: solved Tim Streater <timstreater@greenbee.net> - 2014-06-13 21:16 +0100
                Re: solved Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-13 16:38 -0400
                  Re: solved richard <noreply@example.com> - 2014-06-13 18:29 -0400
                    Re: solved Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-13 19:43 -0400
                      Re: solved richard <noreply@example.com> - 2014-06-13 20:48 -0400
                        Re: solved Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-13 21:39 -0400
                    Re: solved Evan Platt <evan@theobvious.espphotography.com.invalid> - 2014-06-13 21:20 -0700
                    Re: solved Denis McMahon <denismfmcmahon@gmail.com> - 2014-06-14 19:50 +0000
                Re: solved richard <noreply@example.com> - 2014-06-13 18:23 -0400
                  Re: solved Denis McMahon <denismfmcmahon@gmail.com> - 2014-06-14 20:01 +0000
              Re: solved Denis McMahon <denismfmcmahon@gmail.com> - 2014-06-13 20:50 +0000
    Re: function for preserving special characters? Richard Damon <Richard@Damon-Family.org> - 2014-06-13 20:45 -0400
      Re: function for preserving special characters? Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-13 20:51 -0400
        Re: function for preserving special characters? Richard Damon <Richard@Damon-Family.org> - 2014-06-13 22:08 -0400

Page 2 of 2 — ← Prev page 1 [2]

#13843 — Re: solved

On Fri, 13 Jun 2014 19:43:52 -0400, Jerry Stuckle wrote:

> On 6/13/2014 6:29 PM, richard wrote:
>> On Fri, 13 Jun 2014 16:38:04 -0400, Jerry Stuckle wrote:
>> 
>>> On 6/13/2014 4:16 PM, Tim Streater wrote:
>>>> In article <157nwayhe47ig.1exa9x5yqxi59$.dlg@40tude.net>, richard
>>>> <noreply@example.com> wrote:
>>>>
>>>>> On Fri, 13 Jun 2014 15:01:53 -0400, Jerry Stuckle wrote:
>>>>>
>>>>>> On 6/13/2014 2:43 PM, richard wrote:
>>>>>>> On Fri, 13 Jun 2014 10:14:06 -0400, Jerry Stuckle wrote:
>>>>>>>>>> On 6/13/2014 9:57 AM, richard wrote:
>>>>>>>>> On Fri, 13 Jun 2014 00:57:10 -0400, richard wrote:
>>>>>>>>>
>>>>>>>>>> When attempting to transfer records from one table to another,
>>>>> certain
>>>>>>>>>> records refuse to be.
>>>>>>>>>> Such as those with words like "I'm".
>>>>>>>>>> What's even more confusing is, "It's" won't work, but "Cathy's"
>>>>> is ok?
>>>>>>>>>>
>>>>>>>>>> I know there is a procedure in PHP for dealing with this.
>>>>>>>>>> I just can't find it right now.
>>>>>>>>>> Can anyone help on this?
>>>>>>>>>
>>>>>>>>> $a=str_replace("'","\'",$a);
>>>>>>>>> Works just fine.
>>>>>>>>> Thanks for the reminder tim.
>>>>>>>>>
>>>>>>>>
>>>>>>>> That might work for sqllite, but it's definitely the WRONG way to
>>>>> do it
>>>>>>>> in MySQL.
>>>>>>>>> As you continously remind me, this is not an mysql issue.
>>>>>>> The table data could care less what characters are in it.
>>>>>>> mysqli doesn't give a shit either.
>>>>>>>>> if I code the data with a \ in the column cell, the output will
>>>>> show that
>>>>>>> \.
>>>>>>>>> One again you are WRONG!  As evidenced by the failure of the
>>>>> insertions.
>>>>>>> And if you would have checked for errors (as you've been told many
>>>>> times
>>>>>> before), you would have found a MySQL error.
>>>>>>> I remind you if something is not a MySQL issue when it's not a MySQL
>>>>>> issue.  However, you can't learn the difference between PHP and MySQL.
>>>>>>> Here's a hint: PHP doesn't care what's in a string.  So if neither
>>>>> one
>>>>>> cares, why should the INSERT fail?
>>>>>
>>>>> Jerry, you are argumentative here just to be arguing.
>>>>> I did put in an error check.
>>>>> That confirmed that it was the single quotes causing the problem.
>>>>>
>>>>> What's going to happen when you say:
>>>>> insert into tabe VALUES('it's').
>>>>> PHP, not mysqli, kicks back an error right?
>>>>> PHP sees the third single quote as a mismatch.
>>>>> To correct this, you must include a \.
>>>>> Insert into table VALUES('it\'s') is now acceptable.
>>>>
>>>> Can you post the exact PHP statement you were using?
>>>>
>>>> See, if you were doing something like (I don't know the syntax exactly):
>>>>
>>>>  $dbh->mysqli ("insert into table VALUES('it's')");
>>>>
>>>> then if you're using double-quotes (") to delimit the SQL string, PHP
>>>> won't care that you have three single quotes inside it. That's just
>>>> string data to PHP. What will happen is that mysqli will complain,
>>>> because what it gets passed is wrong SQL.
>>>>
>>>> It would still be mysqli complaining if you did this:
>>>>
>>>>  $dbh->mysqli ("three coins in a fountain, said Fred");
>>>>
>>>
>>> Tim,
>>>
>>> No, RTS can't tell the difference between a string containing a single
>>> quote and a string variable containing a single quote.
>> 
>> Jerry, all you're doing now is bashing me.
>> Makes no difference what the issue is, you just have to bash.
>> Besides, you fucked up.
>> You said single quote twice.
>> (Oh but I meant to say that)
>> 
>> You have stepped down to Evan's level.
>> 
> 
> I'm just telling the truth, RTS.  And I know I said single quote twice -
> I meant to.  And anyone with half a brain understands what I said.

Jerry, you have stepped down to evan's level for sure.
this is a string: "It's Late".
this is a variable string: $x="It's Late".

The variable is nothing more than a shortcut.
The variable allows us to use the same information over and over and at
numerous places. We don't have to use a variable but it is there.
It is cvalled a variable because the content can change as desired.


I'm done with you here, asswipe.

[toc] | [prev] | [next] | [standalone]

#13845 — Re: solved

On 6/13/2014 8:48 PM, richard wrote:
> On Fri, 13 Jun 2014 19:43:52 -0400, Jerry Stuckle wrote:
> 
>> On 6/13/2014 6:29 PM, richard wrote:
>>> On Fri, 13 Jun 2014 16:38:04 -0400, Jerry Stuckle wrote:
>>>
>>>> On 6/13/2014 4:16 PM, Tim Streater wrote:
>>>>> In article <157nwayhe47ig.1exa9x5yqxi59$.dlg@40tude.net>, richard
>>>>> <noreply@example.com> wrote:
>>>>>
>>>>>> On Fri, 13 Jun 2014 15:01:53 -0400, Jerry Stuckle wrote:
>>>>>>
>>>>>>> On 6/13/2014 2:43 PM, richard wrote:
>>>>>>>> On Fri, 13 Jun 2014 10:14:06 -0400, Jerry Stuckle wrote:
>>>>>>>>>>> On 6/13/2014 9:57 AM, richard wrote:
>>>>>>>>>> On Fri, 13 Jun 2014 00:57:10 -0400, richard wrote:
>>>>>>>>>>
>>>>>>>>>>> When attempting to transfer records from one table to another,
>>>>>> certain
>>>>>>>>>>> records refuse to be.
>>>>>>>>>>> Such as those with words like "I'm".
>>>>>>>>>>> What's even more confusing is, "It's" won't work, but "Cathy's"
>>>>>> is ok?
>>>>>>>>>>>
>>>>>>>>>>> I know there is a procedure in PHP for dealing with this.
>>>>>>>>>>> I just can't find it right now.
>>>>>>>>>>> Can anyone help on this?
>>>>>>>>>>
>>>>>>>>>> $a=str_replace("'","\'",$a);
>>>>>>>>>> Works just fine.
>>>>>>>>>> Thanks for the reminder tim.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> That might work for sqllite, but it's definitely the WRONG way to
>>>>>> do it
>>>>>>>>> in MySQL.
>>>>>>>>>> As you continously remind me, this is not an mysql issue.
>>>>>>>> The table data could care less what characters are in it.
>>>>>>>> mysqli doesn't give a shit either.
>>>>>>>>>> if I code the data with a \ in the column cell, the output will
>>>>>> show that
>>>>>>>> \.
>>>>>>>>>> One again you are WRONG!  As evidenced by the failure of the
>>>>>> insertions.
>>>>>>>> And if you would have checked for errors (as you've been told many
>>>>>> times
>>>>>>> before), you would have found a MySQL error.
>>>>>>>> I remind you if something is not a MySQL issue when it's not a MySQL
>>>>>>> issue.  However, you can't learn the difference between PHP and MySQL.
>>>>>>>> Here's a hint: PHP doesn't care what's in a string.  So if neither
>>>>>> one
>>>>>>> cares, why should the INSERT fail?
>>>>>>
>>>>>> Jerry, you are argumentative here just to be arguing.
>>>>>> I did put in an error check.
>>>>>> That confirmed that it was the single quotes causing the problem.
>>>>>>
>>>>>> What's going to happen when you say:
>>>>>> insert into tabe VALUES('it's').
>>>>>> PHP, not mysqli, kicks back an error right?
>>>>>> PHP sees the third single quote as a mismatch.
>>>>>> To correct this, you must include a \.
>>>>>> Insert into table VALUES('it\'s') is now acceptable.
>>>>>
>>>>> Can you post the exact PHP statement you were using?
>>>>>
>>>>> See, if you were doing something like (I don't know the syntax exactly):
>>>>>
>>>>>  $dbh->mysqli ("insert into table VALUES('it's')");
>>>>>
>>>>> then if you're using double-quotes (") to delimit the SQL string, PHP
>>>>> won't care that you have three single quotes inside it. That's just
>>>>> string data to PHP. What will happen is that mysqli will complain,
>>>>> because what it gets passed is wrong SQL.
>>>>>
>>>>> It would still be mysqli complaining if you did this:
>>>>>
>>>>>  $dbh->mysqli ("three coins in a fountain, said Fred");
>>>>>
>>>>
>>>> Tim,
>>>>
>>>> No, RTS can't tell the difference between a string containing a single
>>>> quote and a string variable containing a single quote.
>>>
>>> Jerry, all you're doing now is bashing me.
>>> Makes no difference what the issue is, you just have to bash.
>>> Besides, you fucked up.
>>> You said single quote twice.
>>> (Oh but I meant to say that)
>>>
>>> You have stepped down to Evan's level.
>>>
>>
>> I'm just telling the truth, RTS.  And I know I said single quote twice -
>> I meant to.  And anyone with half a brain understands what I said.
> 
> Jerry, you have stepped down to evan's level for sure.

Not at all.  You're the one arguing from a position of ignorance (and
incompetence).

> this is a string: "It's Late".
> this is a variable string: $x="It's Late".
> 
> The variable is nothing more than a shortcut.

No, the variable is MUCH MORE than a shortcut.  But you don't understand
that.

> The variable allows us to use the same information over and over and at
> numerous places. We don't have to use a variable but it is there.
> It is cvalled a variable because the content can change as desired.
> 

Congratulations - you can read the dictionary (don't know if you can
understand it, though).

But you're just proving your stupidity over and over again, arguing
something about which you know nothing.

> 
> I'm done with you here, asswipe.
> 

Thanks you!


-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#13847 — Re: solved

On Fri, 13 Jun 2014 18:29:11 -0400, richard <noreply@example.com>
wrote:

>You have stepped down to Evan's level.

Clueless troll.

You're just upset that I busted you for using a sock puppet because no
one in the SQL group will help your dumb ass.

How's that dome home coming, troll?

Now crawl back under your bridge.
-- 
To reply via e-mail, remove The Obvious and .invalid from my e-mail address.

[toc] | [prev] | [next] | [standalone]

#13851 — Re: solved

On Fri, 13 Jun 2014 18:29:11 -0400, richard wrote:

> On Fri, 13 Jun 2014 16:38:04 -0400, Jerry Stuckle wrote:

>> No, RTS can't tell the difference between a string containing a single
>> quote and a string variable containing a single quote.

> You said single quote twice.

He wasn't wrong. Look at the words preceding "a single quote". The fact 
that you didn't even notice the difference between the two different 
things that he was describing proves he is correct.

-- 
Denis McMahon, denismfmcmahon@gmail.com

[toc] | [prev] | [next] | [standalone]

#13839 — Re: solved

On Fri, 13 Jun 2014 21:16:00 +0100, Tim Streater wrote:

> In article <157nwayhe47ig.1exa9x5yqxi59$.dlg@40tude.net>, richard
> <noreply@example.com> wrote:
> 
>> On Fri, 13 Jun 2014 15:01:53 -0400, Jerry Stuckle wrote:
>> 
>>> On 6/13/2014 2:43 PM, richard wrote:
>>>> On Fri, 13 Jun 2014 10:14:06 -0400, Jerry Stuckle wrote:
>>>> 
>>>>> On 6/13/2014 9:57 AM, richard wrote:
>>>>>> On Fri, 13 Jun 2014 00:57:10 -0400, richard wrote:
>>>>>>
>>>>>>> When attempting to transfer records from one table to another, certain
>>>>>>> records refuse to be.
>>>>>>> Such as those with words like "I'm".
>>>>>>> What's even more confusing is, "It's" won't work, but "Cathy's" is ok?
>>>>>>>
>>>>>>> I know there is a procedure in PHP for dealing with this.
>>>>>>> I just can't find it right now.
>>>>>>> Can anyone help on this?
>>>>>>
>>>>>> $a=str_replace("'","\'",$a);
>>>>>> Works just fine.
>>>>>> Thanks for the reminder tim.
>>>>>>
>>>>>
>>>>> That might work for sqllite, but it's definitely the WRONG way to do it
>>>>> in MySQL.
>>>> 
>>>> As you continously remind me, this is not an mysql issue.
>>>> The table data could care less what characters are in it.
>>>> mysqli doesn't give a shit either.
>>>> 
>>>> if I code the data with a \ in the column cell, the output will show that
>>>> \.
>>>> 
>>> 
>>> One again you are WRONG!  As evidenced by the failure of the insertions.
>>> 
>>> And if you would have checked for errors (as you've been told many times
>>> before), you would have found a MySQL error.
>>> 
>>> I remind you if something is not a MySQL issue when it's not a MySQL
>>> issue.  However, you can't learn the difference between PHP and MySQL.
>>> 
>>> Here's a hint: PHP doesn't care what's in a string.  So if neither one
>>> cares, why should the INSERT fail?
>> 
>> Jerry, you are argumentative here just to be arguing.
>> I did put in an error check.
>> That confirmed that it was the single quotes causing the problem.
>> 
>> What's going to happen when you say:
>> insert into tabe VALUES('it's').
>> PHP, not mysqli, kicks back an error right?
>> PHP sees the third single quote as a mismatch.
>> To correct this, you must include a \.
>> Insert into table VALUES('it\'s') is now acceptable.
> 
> Can you post the exact PHP statement you were using?
> 
> See, if you were doing something like (I don't know the syntax exactly):
> 
>   $dbh->mysqli ("insert into table VALUES('it's')");
> 
> then if you're using double-quotes (") to delimit the SQL string, PHP
> won't care that you have three single quotes inside it. That's just
> string data to PHP. What will happen is that mysqli will complain,
> because what it gets passed is wrong SQL.
> 
> It would still be mysqli complaining if you did this:
> 
>   $dbh->mysqli ("three coins in a fountain, said Fred");

Tim, I experiemented with that.
Double quotes in the values() sends the data in the quotes as is.
eg. values("$string") outputs $string as the data in that columnn.
Not the value you assigned to $string.

[toc] | [prev] | [next] | [standalone]

#13852 — Re: solved

On Fri, 13 Jun 2014 18:23:12 -0400, richard wrote:

>> It would still be mysqli complaining if you did this:

>>   $dbh->mysqli ("three coins in a fountain, said Fred");

> Tim, I experiemented with that.
> Double quotes in the values() sends the data in the quotes as is. eg.
> values("$string") outputs $string as the data in that columnn.
> Not the value you assigned to $string.

That might be because to use double quotes inside the sql statement you 
would have had to use single quotes at the php level, and php handles 
strings quoted with single and double quotes differently.

-- 
Denis McMahon, denismfmcmahon@gmail.com

[toc] | [prev] | [next] | [standalone]

#13838 — Re: solved

On Fri, 13 Jun 2014 15:44:58 -0400, richard wrote:

> What's going to happen when you say:
> insert into tabe VALUES('it's').
> PHP, not mysqli, kicks back an error right?

No. the mysql rdbms kicks the error back to through the mysqli interface 
to php.

PHP really doesn't care what you put in a string.

mysqli->query() (or mysqli_query()) just takes the string you give it and 
passes it to the mysql rdbms as an sql command.

If the string that you assembled in php and passed to the mysql rdbms 
using the mysqli interface is not a valid sql statement, then the mysql 
rdbms indicates this by returning an error value to the mysqli interface 
code which is then passed back to php by setting the result of the mysqli-
>query() (or mysqli_query()) call to false, and also setting an error 
number and an error string which can be retrieved with other appropriate 
mysqli_*() (or mysqli->*()) calls.

> PHP sees the third single quote as a mismatch.

No, PHP isn't seeing the single quote as a mismatch, mysql is seeing the 
single quote as a mismatch. That's why you're getting a mysql error and 
not a php error.

> To correct this, you must include a \.
> Insert into table VALUES('it\'s') is now acceptable.

It might appear to be working in this instance, but it is not the correct 
way to do this. Have you actually checked that the data that ends up in 
the table is what you're assuming it is?

-- 
Denis McMahon, denismfmcmahon@gmail.com

[toc] | [prev] | [next] | [standalone]

#13842

On 6/13/14, 12:57 AM, richard wrote:
> When attempting to transfer records from one table to another, certain
> records refuse to be.
> Such as those with words like "I'm".
> What's even more confusing is, "It's" won't work, but "Cathy's" is ok?
> 
> I know there is a procedure in PHP for dealing with this.
> I just can't find it right now.
> Can anyone help on this?
> 

There are several ways to do this.

The first, is to use "Prepared Statements" to write to the database.
When you do this, you build of the command to perform independent of the
data to process (with place holders), and then connect this to the data
when you execute the prepared statement.

The other option is to use something like mysqli_real_escape_string()
function or mysqli::real_escape_string() (there is also
mysql_real_escaple_string() if you are still using the obsolete mysql
routines). You could also do this with a str_replace, but you need to
determine all the cases that need to be escaped (this isn't as simple as
it might first seem, as the manual implies that this may depend on the
character set selected.

[toc] | [prev] | [next] | [standalone]

#13844

On 6/13/2014 8:45 PM, Richard Damon wrote:
> On 6/13/14, 12:57 AM, richard wrote:
>> When attempting to transfer records from one table to another, certain
>> records refuse to be.
>> Such as those with words like "I'm".
>> What's even more confusing is, "It's" won't work, but "Cathy's" is ok?
>>
>> I know there is a procedure in PHP for dealing with this.
>> I just can't find it right now.
>> Can anyone help on this?
>>
> 
> There are several ways to do this.
> 
> The first, is to use "Prepared Statements" to write to the database.
> When you do this, you build of the command to perform independent of the
> data to process (with place holders), and then connect this to the data
> when you execute the prepared statement.
> 
> The other option is to use something like mysqli_real_escape_string()
> function or mysqli::real_escape_string() (there is also
> mysql_real_escaple_string() if you are still using the obsolete mysql
> routines). You could also do this with a str_replace, but you need to
> determine all the cases that need to be escaped (this isn't as simple as
> it might first seem, as the manual implies that this may depend on the
> character set selected.
> 

Richard,

We've told RTS (Richard the Stupid) this many times but he never learns.
 Then he comes back and insults people who try to help him.

That's the reason the regulars in this newsgroup aren't telling him.
We're tired of him arguing (like he is with me earlier in this thread -
and he's ALWAYS wrong) and insulting the rest of us.

And of course he NEVER apologizes.

Just search this newsgroup for RTS and look at some of the threads.
You'll get an eyeful.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#13846

On 6/13/14, 8:51 PM, Jerry Stuckle wrote:
> 
> Richard,
> 
> We've told RTS (Richard the Stupid) this many times but he never learns.
>  Then he comes back and insults people who try to help him.
> 
> That's the reason the regulars in this newsgroup aren't telling him.
> We're tired of him arguing (like he is with me earlier in this thread -
> and he's ALWAYS wrong) and insulting the rest of us.
> 
> And of course he NEVER apologizes.
> 
> Just search this newsgroup for RTS and look at some of the threads.
> You'll get an eyeful.
> 

I am familiar with the other "richard", and do normally resist getting
too involved in answering. In this case, is others had given BAD answers
(using str_replace, and NOT taking care to handle even all of the normal
cases), I felt a proper answer needed to be added to avoid leading other
readers down the wrong path.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.php

csiph-web