Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:92422 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55979 invoked from network); 18 Apr 2016 18:39:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Apr 2016 18:39:49 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:54210] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0D/FB-11975-3F925175 for ; Mon, 18 Apr 2016 14:39:48 -0400 Received: (qmail 28377 invoked by uid 89); 18 Apr 2016 18:39:44 -0000 Received: by simscan 1.3.1 ppid: 28369, pid: 28373, t: 0.0766s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.7?) (lester@rainbowdigitalmedia.org.uk@81.153.92.101) by mail4.serversure.net with ESMTPA; 18 Apr 2016 18:39:44 -0000 To: internals@lists.php.net References: <57103A46.6040803@garfieldtech.com> <5710BA79.5060108@lsces.co.uk> <57110DC5.8000007@garfieldtech.com> <571338E6.50507@fleshgrinder.com> <57145AF7.7060607@garfieldtech.com> <57149405.2040701@lsces.co.uk> <57151210.7040704@garfieldtech.com> <57152641.7050602@gmail.com> Message-ID: <571529F0.9090106@lsces.co.uk> Date: Mon, 18 Apr 2016 19:39:44 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <57152641.7050602@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Nullable Return Type Declaration From: lester@lsces.co.uk (Lester Caine) On 18/04/16 19:24, Stanislav Malyshev wrote: > If your database died, your DB-bound code is not going > to fix it. With or without nulls - it has to just fail and wait for > somebody to fix it. There's no need to overcomplicate that. If the DB read failed due to the connection being lost, then that is a case for an exception and out of flow events? The 'null' would be returned when an active connection has no data to return because a search or query has produced none. Larry would probably be looking to check the 'no_of_recs' to see if there were any results but then you still have to read the result if there is one ... overcomplicating the simple solution? ( ADOdb check the connection is still valid as part of the query prep and run and changes the work flow if required ) -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk