Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:4913 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68117 invoked by uid 1010); 22 Oct 2003 17:07:12 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 68093 invoked from network); 22 Oct 2003 17:07:11 -0000 Received: from unknown (HELO mail.dybnet.de) (195.75.116.242) by pb1.pair.com with SMTP; 22 Oct 2003 17:07:11 -0000 Received: (qmail 28639 invoked by uid 508); 22 Oct 2003 17:07:20 -0000 Received: from unknown (HELO vandal) (vandal@213.54.28.158) by www.dybnet.de with RC4-MD5 encrypted SMTP; 22 Oct 2003 17:07:20 -0000 To: "'PHP Development'" Date: Wed, 22 Oct 2003 19:06:02 +0200 Organization: BackendMedia GbR MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcOYvsW/5+UzNbPISDyCcs9qRjQdAA== Subject: database driver: no more rows From: smith@backendmedia.com ("Lukas Smith") Message-ID: Hi, I would appreciate it if the database extensions would no longer return false when no rows are left in the result set but instead return null. The current way of returning false creates a level of ambiguity which can lead to serious issue in error handling. For example in mysql there is no way in knowing if you get false and then check for an error if the error was actually created by the fetch call or if the error was created by some other call to any of the mysql functions. Please see this bug for another example: http://bugs.php.net/bug.php?id=22328 Regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07