No worries, Anthony!
Am 15.06.2012 21:15, schrieb Anthony Ferrara:
I would commit, but I do not have commit access (no karma at all). I'm
going away for a few days, but when I get back I will send a separate
request to the list for karma.
I see. It is not up to me to grant karma. I am not tha
Ulf,
My apologies. I mis-interpreted that reply.
I would commit, but I do not have commit access (no karma at all). I'm
going away for a few days, but when I get back I will send a separate
request to the list for karma.
Thanks,
Anthony
On Fri, Jun 15, 2012 at 1:55 PM, Ulf Wendel wrote:
> Am
Am 15.06.2012 19:31, schrieb Anthony Ferrara:
Ulf,
It needs an RFC because it needs to document whether or not the other
DB drivers should also be changed.
It's a PDO driver-specific change. So to me it's fairly straight
forward to see that no other drivers need changing... It doesn't even
hi
Ulf,
>>> It needs an RFC because it needs to document whether or not the other
>>> DB drivers should also be changed.
>>
>>
>> It's a PDO driver-specific change. So to me it's fairly straight
>> forward to see that no other drivers need changing... It doesn't even
>> hit the mysql API level...
>>
>
Am 15.06.2012 18:36, schrieb Anthony Ferrara:
Chris,
Does this need to be an RFC (should I draft one)? Or can it just be
pulled as-is?
It needs an RFC because it needs to document whether or not the other
DB drivers should also be changed.
It's a PDO driver-specific change. So to me it's f
On 06/15/2012 09:36 AM, Anthony Ferrara wrote:
Chris,
Does this need to be an RFC (should I draft one)? Or can it just be
pulled as-is?
It needs an RFC because it needs to document whether or not the other
DB drivers should also be changed.
It's a PDO driver-specific change. So to me it'
Chris,
>>> Does this need to be an RFC (should I draft one)? Or can it just be
>>> pulled as-is?
>
>
> It needs an RFC because it needs to document whether or not the other
> DB drivers should also be changed.
It's a PDO driver-specific change. So to me it's fairly straight
forward to see that no
Am 15.06.2012 03:01, schrieb Anthony Ferrara:
I raised this topic on list over a year ago (
http://marc.info/?l=php-internals&m=130417646507744&w=2 ). It was
determined that it wasn't time yet to disable prepared statement
emulation for MySQL yet.
Does this need to be an RFC (should I draft
This userland library already solves all the issues you outlined with
bcrypt: http://www.openwall.com/phpass/
The API is very easy to use, has been around for a while and has a
number of detailed articles that explain how to use it.
--
Herman Radtke
hermanrad...@gmail.com | http://hermanradtke.c
Am 15.06.2012 03:01, schrieb Anthony Ferrara:
I raised this topic on list over a year ago (
http://marc.info/?l=php-internals&m=130417646507744&w=2 ). It was
determined that it wasn't time yet to disable prepared statement
emulation for MySQL yet. However, Rasmus did mention that it was a
possibi
10 matches
Mail list logo