iven different
constants.
> -Original Message-
> From: Johan De Meersman [mailto:vegiv...@tuxera.be]
> Sent: Monday, May 14, 2012 9:17 AM
> To: Reindl Harald
> Cc: mysql@lists.mysql.com
> Subject: Re: MySQL Community Server 5.1.63 has been released
>
>
>
>
What you do recommend in place of mysql_real_escape_string()?
> -Original Message-
> From: Govinda [mailto:govinda.webdnat...@gmail.com]
> Sent: Monday, May 14, 2012 7:34 AM
> To: Johan De Meersman
> Cc: mysql@lists.mysql.com
> Subject: Re: MySQL Community Server 5.1.63
- Original Message -
> From: "Reindl Harald"
>
> but what about the dramatical reduced query-cache hits i see
> in some peace of software switching to prepared statements?
>
> dbmail2 as example had around 300 sql-actions per second
> dbmail3 using prepared statements currently around
Am 14.05.2012 16:50, schrieb Johan De Meersman:
> - Original Message -
>> From: "Govinda"
>>
>> 1.) Is anyone *who knows what he is doing* still using
>> mysql_real_escape_string()? Ever?
>
> I seem to vaguely remember someone showing me some code that would bypass
> escaping; but I d
- Original Message -
> From: "Govinda"
>
> 1.) Is anyone *who knows what he is doing* still using
> mysql_real_escape_string()? Ever?
I seem to vaguely remember someone showing me some code that would bypass
escaping; but I didn't really pay a lot of attention, to be honest :-)
Person
Bugs Fixed
* Security Fix: Bug #64884 was fixed.
* Security Fix: Bug #59387 was fixed.
>>>
>>> Anyone want to elaborate on the nature or severity of the security
>>> problem? Both are private / inaccessible to me.
>>
>> Bug #64884 was apparently also applicable to, and fixed
- Original Message -
>
> > From: "Baron Schwartz"
> >
> >> Bugs Fixed
> >> * Security Fix: Bug #64884 was fixed.
> >> * Security Fix: Bug #59387 was fixed.
> >
> > Anyone want to elaborate on the nature or severity of the security
> > problem? Both are private / inaccessible t
- Original Message -
> From: "Baron Schwartz"
>
>> Bugs Fixed
>> * Security Fix: Bug #64884 was fixed.
>> * Security Fix: Bug #59387 was fixed.
>
> Anyone want to elaborate on the nature or severity of the security
> problem? Both are private / inaccessible to me.
Bug #64884
Hi,
> D.1.1. Changes in MySQL 5.1.63 (7th May, 2012)
>
> Bugs Fixed
>
> * Security Fix: Bug #64884 was fixed.
>
> * Security Fix: Bug #59387 was fixed.
Anyone want to elaborate on the nature or severity of the security
problem? Both are private / inaccessible to me.
--
MySQL General Ma
