Bug #11920 Updated: e.g. mysql_unbuffered_query doesn't function but throws no error to indicate

ID: 11920 Updated by: mfischer Reported By: gwelters@weos.de Old Status: Open Status: Bogus Bug Type: MySQL related Operating System: linux PHP Version: 4.0.5 New Comment: Thanks for the info. But we won't release a bugfixed version of 4.0.5. Developers try hard but sometimes everyone makes a mistake. Btw, if you still have memory management problems with 4.0.6 give it a try with latest RC http://www.php.net/~zeev/php-4.1.0RC3.tar.gz Not really a bug anymore, bogus. Previous Comments: ------------------------------------------------------------------------ [2001-07-06 04:20:06] gwelters@weos.de It's a BIG BIG Problem to find the reason why your application doesn't work when there's NO indication that a implemented php-function does NOT what it should do, without trowing any error! Thats what happened as I tried to move back from 4.0.6 to 4.0.5 due to a BIG bug in the memory-management of 4.0.6: for 4.0.6 I replaced mysql_query with mysql_unbuffered_query in one function. There was no Prob with that in 4.0.6...but after I had 4.0.5 back again my app didn't work anymore without giving any indication of the reason. It would be great if the php-developers could provide a bit more error-messages for instance when mysql_unbuffered_query works only for SELECT's, not for INSERT's, why not throw a WARNING or ERROR if you try to use the wrong query. this would avoid Days of debugging! ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=11920&edit=1