What are the differences between addslashes(), mysql_escape_string() and mysql_real_escape_string()
addslashes() escapes single quote (’), double quote ("), backslash (\) and NUL (\x00).
mysql_escape_string() and mysql_real_escape_string() escapes the characters above plus: CR (\r), LF (\n) and EOF (\x1a). Apparently (according to the manual), MySQL wants these characters escaped too, but my experiment shows otherwise (i.e. MySQL doesn’t care if these characters are in a string).
$value = 'ba r'; // 'ba' and then CR-LF and then 'r'
print “insert into pairs values (‘foo’, ’” . addslashes($value) . “’)” gives:
insert into pairs values ('foo', 'ba\r\nr')
print “insert into pairs values (‘foo’, ’” . mysql_real_escape_string($value) . “’)” gives:
insert into pairs values ('foo', 'ba r')
In this case, the execution result should be the same, but the statement itself is different.
For other EOF, the execution result and statement are identical for both functions.
mysql_real_escape_string() is available on PHP 4.3.0 or above. mysql_escape_string() is deprecated and you should use mysql_real_escape_string() instead, as it takes the current character set into account when escaping characters.
addslashes() should be enough for single-byte strings. For multi-byte strings though,
mysql_real_escape_string() does provide better security. See this article for details.
PHP manual on: