Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71639 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92967 invoked from network); 27 Jan 2014 13:45:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jan 2014 13:45:19 -0000 Authentication-Results: pb1.pair.com header.from=arvids.godjuks@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=arvids.godjuks@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.53 as permitted sender) X-PHP-List-Original-Sender: arvids.godjuks@gmail.com X-Host-Fingerprint: 209.85.216.53 mail-qa0-f53.google.com Received: from [209.85.216.53] ([209.85.216.53:58360] helo=mail-qa0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 44/35-12631-EE266E25 for ; Mon, 27 Jan 2014 08:45:19 -0500 Received: by mail-qa0-f53.google.com with SMTP id cm18so7109695qab.40 for ; Mon, 27 Jan 2014 05:45:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=sRFxaliQ6AHHpGZXfMNVfiR1NBVOCzv6HWhp26NDYUs=; b=ltilX1KUQ0OswMhSxLMTq+9/fxqBZjtGtVj91AbCBtxlDn/OAOL3ODgaPJigCr/RNV trbDBxPQza7rxHAcvUFjkki7dp1o88wqSTktM8ugkv+AiGyWKBvQbq+4znFQIMErmqUO /dg89+xXpXzmNCs7wxNn0q+yI0A+eKF+oDy6i8FetrC6hR+9E7LcuhVdzCOwthhLDRAY t4Io7QHkU1PJKxilP5yj5Gk+tKmZ9q6OewNLy1j4KGEgjlysLbaLyqBOEYshsN+BLola +f7+6ul//MzoScjeDL/xKzwvX6EQfXslOrmcBCfXjuYwGRPRi2/Qvey08xIfY5Nvc3i7 9J7g== X-Received: by 10.224.72.72 with SMTP id l8mr42728969qaj.51.1390830316008; Mon, 27 Jan 2014 05:45:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.97.182 with HTTP; Mon, 27 Jan 2014 05:44:55 -0800 (PST) In-Reply-To: <52E65975.5040508@lsces.co.uk> References: <52E29253.2000801@lsces.co.uk> <52E2924B.6080002@ajf.me> <52E299D4.6040102@garfieldtech.com> <52E2C98C.6010005@lerdorf.com> <52E2D8D2.80106@lerdorf.com> <52E64D10.5020404@hristov.com> <52E65975.5040508@lsces.co.uk> Date: Mon, 27 Jan 2014 15:44:55 +0200 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary=047d7bf0e1f6edbb8404f0f3eaf3 Subject: Re: [PHP-DEV] Ruminations on PHP 5++ From: arvids.godjuks@gmail.com (Arvids Godjuks) --047d7bf0e1f6edbb8404f0f3eaf3 Content-Type: text/plain; charset=UTF-8 2014-01-27 Lester Caine > Arvids Godjuks wrote: > >> With your permission, I want to start that "Future of PDO" thread, laying >> out my personal experience with it and some thought for the future to >> invite the discussion. >> > > Well there is a list for discussing PDO, but there has only been one post > in the last few months. I'm not sure that pushing the discussion over there > would help any? It needs a wider discussion on database support in general? > > > -- > Lester Caine - G8HFL > I'm a userland PHP developer, so I can't speak to the internals of PDO and how it is coded. But as I spoke to people and read all kinds of stuff about PDO (and I talked on this topic a lot with Julien Pauli when he was visiting for a conference), PDO has some big issues on it's development side and internals, that should be taken care of before there is a wide audience discussion on the userland side. So my thinking is that at this point it warants a php-internals discussion first. And then, depending on that discussions outcome, init a wide audience discussion on the future of PDO with PHP-FIG and others. But I want to re-iterate, and I can be wrong: PDO is a huge undertaking by it's nature and as far as I know, there is not much work been done since it's release and has a lot of technical dept accumulated (just see the giant difference between the PDO and most of the native drivers functionality wise). Internals should decine what to do with it in the first and are there resources to even bother with it (I had a few hints that people just don't want go near the PDO). Also, a concern of mine is that if we start with a more broad discussion right away, it may end up in a flamewar, unconstructive discussion and people pushing their own ideas too much - all of what can lead to another "Hint typing" monster thread. --047d7bf0e1f6edbb8404f0f3eaf3--