At 10:24 AM 5/3/2001 -0500, Andrei Zmievski wrote:
>On Thu, 03 May 2001, Andi Gutmans wrote:
> > >Also, have you seen people complain about my patch to MySQL that adds
> > >NULL's to the result set?
> >
> > No because isset() returns false for NULL values. But many people would
> > like it to return true, and then it would break people's scripts. I guess
> > at that point we could change the MySQL module back and not really break
> > people's scripts.
>I have a definite need to know whether $row['foo'] is NULL or not. Can
>you propose a solution towards that? If you revert the patch, then the
>result set will look as if column 'foo' was never returned.

How do you know today if it's NULL or not?
You can't really tell. It does effect array traversal.
I'm not saying it's right or wrong now. I'm just trying to think ahead 
especially as there are mixed feelings about how NULL should behave.


PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to