"bruce" <[EMAIL PROTECTED]> wrote on 09/22/2005 09:15:56 PM:
> hi...
>
> from the docs... it appears the the mysql_real_escape_string function
(from
> php) is used to backslash a set of chars in the string for insertion
into
> the mysql db...
>
> however, given that the '/' is mysql, vs ansi,
bruce wrote:
from the docs... it appears the the mysql_real_escape_string function (from
php) is used to backslash a set of chars in the string for insertion into
the mysql db...
however, given that the '/' is mysql, vs ansi, i was wondering if there's a
way to force it to use the ansi standard
hi...
from the docs... it appears the the mysql_real_escape_string function (from
php) is used to backslash a set of chars in the string for insertion into
the mysql db...
however, given that the '/' is mysql, vs ansi, i was wondering if there's a
way to force it to use the ansi standard "'" inst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again
After further inspection of libmysql sources the conclusion is:
- - mysql_real_escape_string() uses MYSQL->charset field from the MYSQL
struct
- - this field is initilized in mysql_real_connect()
- - so after my connection times out I should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
- From the online docs:
"The string in from is encoded to an escaped SQL string, taking into
account the current character set of the connection."
Lets say I have a connection, setup, working, then it timesout (server
side, ex. because of "wait_
