> From: Andi Gutmans [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 23, 2003 12:06 AM > >I don't think I've had any experince with those functions returning FALSE > >for me, but I think it's more logical that they differentiate between the > >FALSE and the NULL for the reasons stated above. > > How is this dealt with today?
Well when you get a return value of false you check if there is an error. But in some ext there is no way in easily determining if an error was created by the fetch call or by some other function call to the ext. run query that works run query that doesn't now when you fetch the rows of the first query you will usually determine if you hit the end if the result set by checking if you don't get an array returned if you don't get an array you check for an error and in several ext you will get the error created by the second query. This is also caused by the fact that the error checking simply returns the last error which cant be cleared appearently. this effectively means that for example in the mysql, mssql, sybase (maybe some other drivers) in PEAR DB we had to remove error checking in the fetch method. But I guess you are right .. this is just a minor limitation and if you are reluctant to accept a BC break to clean up minor limitations then its not something that will ever get fixed (it could of course be fixed in new extensions). Regards, Lukas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
