Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100866 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42962 invoked from network); 12 Oct 2017 08:23:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Oct 2017 08:23:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=pass Received-SPF: pass (pb1.pair.com: domain lsces.co.uk designates 185.153.204.204 as permitted sender) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 185.153.204.204 mail4.serversure.net Linux 2.6 Received: from [185.153.204.204] ([185.153.204.204:47852] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2B/B1-49033-D662FD95 for ; Thu, 12 Oct 2017 04:23:10 -0400 Received: (qmail 25738 invoked by uid 89); 12 Oct 2017 08:23:06 -0000 Received: by simscan 1.3.1 ppid: 25732, pid: 25735, t: 0.0400s 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.138.11.136) by mail4.serversure.net with ESMTPA; 12 Oct 2017 08:23:06 -0000 To: internals@lists.php.net References: <050ebe9b36b83431a4f2d5c170de57ad@bohwaz.net> <1aecde71827b7e65422dd6243e74a67b@bohwaz.net> Message-ID: <37cffef9-dbd4-eb8c-699f-6fb427bb0684@lsces.co.uk> Date: Thu, 12 Oct 2017 09:23:06 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <1aecde71827b7e65422dd6243e74a67b@bohwaz.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] [VOTE] Implement missing SQLite feature "openBlob" in PDO From: lester@lsces.co.uk (Lester Caine) On 12/10/17 00:11, BohwaZ/PHP wrote: >> I think people were reasonably clear during the discussion. >> >> Having certain methods only available on an object depending on how it >> was initialized is just not a good idea. > > As far as I know, no one volunteered to rewrite PDO to change that? > > I don't really understand that logic. Yeah the existing behaviour is not > optimal. But there is no other solution right now. > > Should we also stop adding any feature to PHP because most PHP functions > are named incoherently and we need to wait until all of them are renamed > correctly? Hopefully not :) > > It might be years (or never) before that PDO behaviour is changed. In > the meantime PHP will just be missing features that could have been > provided, this sounds strange to me. The 'other solution' right now is to ensure that the generic drivers for each database API do the right thing, and if you must use generic features then use those drivers. PDO SHOULD only provide the lowest common denominator of data abstraction that works CLEANLY independent of the driver selected. That has already been messed up by some of the 'extras' added to individual drivers and it is about time the ground rules were clearly defined and enforced. That nobody has stepped up to finish the parts of PDO that were put on the back burner when it was prematurely pushed into the core build is perhaps a further indication that it was not the right base from the start? -- 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