# database driver: no more rows

- Thread: https://externals.io/message/4924
- Original archive: https://news-web.php.net/php.internals/4924
- Started by GPHemsley@aol.com on 2003-10-22T22:04:58+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #4924 — GPHemsley@aol.com — 2003-10-22T22:04:58+00:00

URL: https://externals.io/message/4924#4924

In a message dated 10/22/2003 6:00:11 PM Eastern Daylight Time, andi@zend.com 
writes:
At 11:49 PM 10/22/2003 +0200, Ard Biesheuvel wrote:
> > […]
>
>Maybe historically (PHP-wise) it does.
>But the way I see it, every fetch() can 'fail' for two reasons: an 
>expected well-defined reason (eof), and an unexpected undefined reason 
>(error). Labelling the well-defined reason as 'false' and the undefined 
>reason as 'null' is really quite defendable.


This isn't something I'd like to see changed. I actually think there are 
probably lots of people who do !== false and we could screw up a lot of 
scripts. I see the advantage of being able to tell the difference but I 
think it's not big enough to change it now.

Andi
Well, this would be my first time contributing to any discussion on this list 
since I joined, but I have a question. 

It was suggested that this be implemented in PHP 5.0.0. Isn't PHP 5 so much 
different than PHP 4 that scripts would have to be somewhat rewritten for it 
anyway? (I'm not saying that PHP 5 is totally different, just different enough.)

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.

Gordon Hemsley

---

## #4925 — Andi Gutmans — 2003-10-22T22:06:28+00:00

URL: https://externals.io/message/4924#4925 · In reply to: #4924

At 06:04 PM 10/22/2003 -0400, GPHemsley@aol.com wrote:

>Well, this would be my first time contributing to any discussion on this 
>list since I joined, but I have a question.
>
>It was suggested that this be implemented in PHP 5.0.0. Isn't PHP 5 so 
>much different than PHP 4 that scripts would have to be somewhat rewritten 
>for it anyway? (I'm not saying that PHP 5 is totally different, just 
>different enough.)
>

For PHP applications which are mostly functional there will be very little 
which will need to be fixed (if at all). Many OOP applications will also 
work and only some will need fixing. There will hopefully be a relative 
small amount of BC problems, and where BC was broken it was usually only 
when it was crucial.

>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?

Andi