Yes, I did send in a patch just like the 3 or 4 other people who had the same problem. I'm not complaining about php, I was just commenting about the person complaining that it was a problem with phpmyadmin. I complained about the problem over a year ago, when I first installed mysql 4.1.0, but the problem was definitely not with phpmyadmin. It was a combination of php not working well with mysql 4.1.0.
How is this a 'problem' with PHP? It was MySQL who changed how passwords were handled by default. However, it's not even a MySQL problem...it's not a problem at all. MySQL added in backwards capabiilty for passwords.
Why would have pay somebody 40k a year, I can do it myself or anyone of my other 20 programmers. When php says it's not a bug, then obviously they don't see it as being a problem.
It's not a problem. There is a workaround for it. It's that simple. Why should the PHP people rewrite the MySQL functions when a) the amount of people using php v4.x and MySQL >= 4.1.x are small, and b) it will work if you take the time to read.
Since all 32 bit servers will be phased out by mid-May because of the opteron and the new intel procs, I'll just sit back and watch the bug submissions come in next year as everybody gets their new hardware in.
All phased out by mid-May??? All where? Maybe at Intercosmos (even though I doubt that), but 32 bit servers will still exist, more that likely as the majority, long after May. Most companies are not going to shell out the duckies to 'upgrade' to 64-bit when a) alot of the software hasn't been battle tested, b) there are no big advantages to it in the LAMP world, and c) there is no big outcry from the customer base to make the switch.
I won't complain, I know how to fix it.
And I'll refrain from getting personal.
-- By-Tor.com ...it's all about the Rush http://www.by-tor.com
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
