Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:4916 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38966 invoked by uid 1010); 22 Oct 2003 17:56:12 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 38922 invoked by uid 1007); 22 Oct 2003 17:56:12 -0000 Message-ID: <20031022175612.38921.qmail@pb1.pair.com> To: internals@lists.php.net Date: Wed, 22 Oct 2003 19:55:52 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 References: <200310221318.27225.ilia@prohost.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 81.166.5.188 Subject: Re: [PHP-DEV] database driver: no more rows From: abies@php.net (Ard Biesheuvel) >>I wouldn't mind such a change myself, however what about all the >>installations >>where people do while (*fetch_row() !== false) ? Wouldn't it be a lot easier to do it the other way around ? I mean, the semantics of returning false when a fetch cannot be executed because aren't any rows left is perfectly clear, and returning NULL when the result cannot be determined (because of an error) is also better than returning any other value (like 'false'). This would also be easier to carry out while maintaining BC. -- Ard