Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85928 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 64649 invoked from network); 23 Apr 2015 14:02:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Apr 2015 14:02:19 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; 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:34019] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AE/3F-35080-66BF8355 for ; Thu, 23 Apr 2015 10:02:18 -0400 Received: (qmail 13850 invoked by uid 89); 23 Apr 2015 14:02:04 -0000 Received: by simscan 1.3.1 ppid: 13757, pid: 13834, t: 0.1763s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 23 Apr 2015 14:02:04 -0000 Message-ID: <5538FB46.9090701@lsces.co.uk> Date: Thu, 23 Apr 2015 15:01:42 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: internals@lists.php.net References: <5537826A.9010209@gmx.de> <5538881C.8010502@oracle.com> <5538C2A7.4050600@lsces.co.uk> <5538CF4B.5090401@beccati.com> <5538D9B0.5020507@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: PDO Oracle driver From: lester@lsces.co.uk (Lester Caine) On 23/04/15 14:45, Arvids Godjuks wrote: > My thinking is that things like these have to be spearheaded by the > respective database developers with the help of the PHP core team and the > community. I am still reliant on ADOdb and have on a number of occasions back ported to that where projects have 'upgraded' to PDO. I still see no reason for everybody to be reinventing the wheel when we HAD a perfectly practical solution 10+ years ago. It would be nice to restore it's speed-up extension once again and certainly I will be ensuring everything works with PHP7. There are a number of other layers, but all PDO seems to have done is fragment the code base with everybody doing their own thing SQL abstraction wise, rather than our producing a standard such as ADOdb provides? The good thing is that replacing PDO with something else at the base level is not a major exercise as most frameworks don't call it direct anyway :) -- 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