Re: Re: Release process
| From: | Zeev Suraski | Date: | Thu, 03 May 2001 14:00:32 +0000 |
| Subject: | Re: Re: Release process | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-53610@lists.php.net to get a copy of this message | ||
Hmmm, looks like the MySQL module was changed to add NULL elements to the array. It even looks as if you changed it :)
I intentionally removed the code that populated return values with NULL's, to avoid inconsistencies. People should use the mysql_fetch_field() to check which fields there are.
I'd like to change it back...
Zeev
At 16:53 3/5/2001, Andrei Zmievski wrote:
On Thu, 03 May 2001, Andi Gutmans wrote: Yeah but I'm afraid it'll make scripts be written on behavior which shouldn't be counted on. Maybe in future versions of Zend $array['foo'] won't be defined. There are certain situations where I think it was impossible to not define it so it was defined with NULL meaning it's not defined. Um, but some db extensions return NULL values as part of the array, so if column 'foo' is NULL in the db, you'd want the result array to have NULL under key 'foo' - it just won't do to have that column be missing. -Andrei * We reason deeply, when we forcibly feel. *-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/