Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85916 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 28525 invoked from network); 23 Apr 2015 10:45:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Apr 2015 10:45:59 -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:55439] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 31/5A-35080-66DC8355 for ; Thu, 23 Apr 2015 06:45:58 -0400 Received: (qmail 24774 invoked by uid 89); 23 Apr 2015 10:45:55 -0000 Received: by simscan 1.3.1 ppid: 24767, pid: 24771, t: 0.0722s 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 10:45:55 -0000 Message-ID: <5538CD62.5060407@lsces.co.uk> Date: Thu, 23 Apr 2015 11:45:54 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: PHP internals References: <5537826A.9010209@gmx.de> <5538881C.8010502@oracle.com> <5538C2A7.4050600@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Re: PDO Oracle driver From: lester@lsces.co.uk (Lester Caine) On 23/04/15 11:22, Arvids Godjuks wrote: > чт, 23 Апр 2015, 13:00, Lester Caine : > > On 23/04/15 06:50, christopher jones wrote: >> > Yes, we do recommend using OCI8 over PDO_OCI. This is partly due to >> > some inherent design and performance weaknesses of the overall PDO >> > architecture. >> > >> > So, lets not mark PDO_OCI as dead just yet. > It's nice to hear that it's not only the pdo_firebird driver that is > restricted by PDO. Which why I was asking for a general review on the > situation on database access. > > I can definetly make a case that PDO restricts MySQL too. It lacks a lot of > functionality comparing to mysqli. I also found out recently that you can't > have a named param appear in a query more than once (an OR case, where 2 > fields are compared against sma e value). The more you work, the more you > understand that PDO was a hype, that never got finished and got almost > abandoned. Now that is that sort of feedback I was not expecting ... I don't use MySQL so to see that it has some inherent problems with PDO as most of the other databases is news. I think PDO is probably now too embedded in some projects to roll back but certainly it's limitations need to be better documented? Some of it's restrictions can not be solved by changes to the code, they are incompatible with the base format, but there is nothing explaining that. -- 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