Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100289 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92127 invoked from network); 23 Aug 2017 10:42:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Aug 2017 10:42:58 -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:58894] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 52/BC-34801-F2C5D995 for ; Wed, 23 Aug 2017 06:42:57 -0400 Received: (qmail 26561 invoked by uid 89); 23 Aug 2017 10:42:52 -0000 Received: by simscan 1.3.1 ppid: 26554, pid: 26557, t: 0.0412s 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; 23 Aug 2017 10:42:52 -0000 To: internals@lists.php.net References: <1e398f12adbdbed6b7caf3b0af07f284@bohwaz.net> <069c08bfe15b856007debab5d0d961be@bohwaz.net> <7b50581b7b2b96920867de76f75c0dfd@bohwaz.net> <61a5739f15f3a645fd9406fa44fa3f59@bohwaz.net> Message-ID: <88934c3a-f224-0cbf-b332-12dc7656864c@lsces.co.uk> Date: Wed, 23 Aug 2017 11:42:52 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <61a5739f15f3a645fd9406fa44fa3f59@bohwaz.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Matching PDO_SQLite features with SQLite3 extension From: lester@lsces.co.uk (Lester Caine) On 23/08/17 06:15, BohwaZ/PHP wrote: > I'm not gonna create another way of having driver-specific features that > wouldn't make sense in relation to existing methods, and I don't have > time to rewrite a significant part of PDO that would cause a major > BC-break. The original intention of PDO was that it did not matter just what underlying database you were using, anything written for one would simply work with any other. All of the driver specific extensions make a mockery of that, and in many cases today PDO will only work with the database it was programmed for ... so why use PDO at all in that instance? For example a BLOB improvement to PDO should work transparently across all databases that support blobs ... and error when blobs are not available. -- 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