#48290 [WFx]: auto escape for variables in double quotes sql string
| From: | kexianbin at diyism dot com | Date: | Tue, 10 Nov 2009 09:53:42 +0000 |
| Subject: | #48290 [WFx]: auto escape for variables in double quotes sql string | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-144405@lists.php.net to get a copy of this message | ||
ID: 48290
User updated by: kexianbin at diyism dot com
-Summary: auto escape for double quotes sql string
Reported By: kexianbin at diyism dot com
Status: Wont fix
Bug Type: Feature/Change Request
Operating System: Irrelevant
PHP Version: 5.3.2
New Comment:
Changed the title to "auto escape for variables in double quotes sql
string".
Previous Comments:
------------------------------------------------------------------------
[2009-11-10 09:51:53] kexianbin at diyism dot com
Changed the title.
------------------------------------------------------------------------
[2009-11-10 09:39:51] kexianbin at diyism dot com
Must have a solution in the world.
If we can't build the auto escape for double quotes sql string,
we can build get_caller_vars to realize the simpler auto escape of
double quotes sql string.
------------------------------------------------------------------------
[2009-11-10 07:45:21] rasmus@php.net
We are trying to get rid of features like addslashes, not make more
similar ones.
------------------------------------------------------------------------
[2009-11-10 07:18:53] kexianbin at diyism dot com
I still wanna reopen this request very much,
If anybody could realize this that will give PHP a special advantage
over other languages.
------------------------------------------------------------------------
[2009-11-10 07:11:10] kexianbin at diyism dot com
Rasmus,
Similar to this in php.ini file:
//Use Sybase-style magic quotes (escape ' with '' instead of \').
magic_quotes_sybase = Off
we could add "double_quotes_escape_for_db = mysql" into php.ini.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/48290
--
Edit this bug report at http://bugs.php.net/?id=48290&edit=1