Hi Ryan, Don't be hasty. What i'm simply saying is that QA is a process and you need to build feedback into the loop. Developers come and go in an Open Source development process and you need to build in regression tests so that when new developers with new ideas come along, they don't break code, or quickly realize what they have done after they have run basic regression tests.
I also think that PHP developers are doing a fine job, but I don't think there is anything wrong in pointing out where they can improve, rather than apologize wholesale. Regards, John "Ryan Jameson" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... We will agree to disagree. I've experienced many testers who thought things that you think. They were often the most cocky and least effective of the hundreds I've worked with on projects, and again every product I've worked with from Microsoft to Oracle to Java have had similar issues arise. I think the PHP developers are doing a fine job, even if I do have to skip a release, I've got my money on this being fixed in the next release. <>< Ryan -----Original Message----- From: John Lim [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 30, 2002 2:50 AM To: [EMAIL PROTECTED] Subject: Re: [PHP-DB] ODBC problem in 4.2.0 Hi Ryan, It's not true that this can happen to any product. PHP is a fantastic language, but there are well-known ways to manage QA. All it needs is to include ODBC in the standard php regression test suite (and run the suite regularly!) Regards, John "Ryan Jameson" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... BTW... I'd just like to point out that this kind of thing is bound to happen no matter what product you use. I'm certain the PHP guys will have this solved in no time and I'd bet even they would recommend a commercial hosting service be willing and able to step back if a problem like this occurs. This is, however, just an opinion. -----Original Message----- From: Ryan Jameson (USA) Sent: Monday, April 29, 2002 8:14 PM To: [EMAIL PROTECTED] Subject: RE: [PHP-DB] ODBC problem in 4.2.0 I'd recommend finding a hosting service that would be more careful about making upgrades. There seems to be some problems with ODBC in 4.2 and I have yet to hear of a work around, especially not one you can implement if you don't handle your own server. I feel your pain man! Fortunately for me I can just stay at 4.1.1 until there's a release that works. <>< Ryan -----Original Message----- From: Mihai Tache [mailto:[EMAIL PROTECTED]] Sent: Monday, April 29, 2002 7:11 PM To: [EMAIL PROTECTED] Subject: [PHP-DB] ODBC problem in 4.2.0 i work on a website that runs on php with MSSQL through ODBC. until 4.2.0 everything was ok. but my hosting provider just upgraded to 4.2.0 the error message i get is : SQL error: [Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt, SQL state S1000 in SQLExecDirect in .... take the folowing code for example : <? $res=odbc_exec($conn,"select * from ..."); for($i=1;odbc_fetch_row($res);$i++) { $res2=odbc_exec($conn,"select * from ...."); ... } ?> the first odbc query runs OK but i get the error at the second one and ONLY if the first one returned more than one row. i even tried with 2 ODBC connections but doesn't work MS has something to say about this at http://support.microsoft.com/default.aspx?scid=kb;EN-US;q143032 don't know if that is really the problem or not. i don't know how i can set ODBC (from php) to be synchronous anyway. the fact is that the same scripts worked fine 6h ago on 4.1.1 and 4.0.6 (both on win32). i'd go back to 4.1.1 but i'm forced to work with 4.2.0 as i said is there something i can do except wait for 4.2.1 ? -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
