Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100283 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65840 invoked from network); 23 Aug 2017 04:31:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Aug 2017 04:31:15 -0000 Authentication-Results: pb1.pair.com smtp.mail=ocramius@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ocramius@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.176 as permitted sender) X-PHP-List-Original-Sender: ocramius@gmail.com X-Host-Fingerprint: 209.85.128.176 mail-wr0-f176.google.com Received: from [209.85.128.176] ([209.85.128.176:34848] helo=mail-wr0-f176.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B1/3A-34801-2150D995 for ; Wed, 23 Aug 2017 00:31:14 -0400 Received: by mail-wr0-f176.google.com with SMTP id k46so1687517wre.2 for ; Tue, 22 Aug 2017 21:31:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=m5GtPqTPlwEH/z9nSWvfCoAvEITukihuxpiX1BQplWc=; b=X7WPlkyqEUcJnHGKPuBEWe38WmphVdAMINlA3IGXK4xUMyrE3d/O7h4lnwHh02q3MD E+UZdIHRzWyFiXzTyQ/bDQm8axMiRfrD8SR6wHgMu4ygxIt5VFDEwitilq5M4ik8MPIs +F82IQjSi4Dh5I9vleniQ62F63O1rWBsSqi7HqRYALIFfvO3wwFwxFau5ffAG2NUWrja ZTye5pYsrmAcFVWqLR/t5XJSfNfKIfaOsZgF0i6Qik4CLtWlciMJgUioxIw556vIxMwR ZeKT3bOaGhTqU6r33Ls8D21V2IizY9oRyb4sAECy62CRGNJ0lBqRwpm7DfupPNRKeU94 mv8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=m5GtPqTPlwEH/z9nSWvfCoAvEITukihuxpiX1BQplWc=; b=bTV59vyc9vWuGWdLnHxkHre0i936eiGWYlELvZyFOqr23JRZsP7SmCV9kNuvfPUOby yh+EN2PuqAmbsqwvgaTvoj97zuo+xE2JVscq/2tHaf2v4TO+f0y5mAD7SgHXOspwTJKd 6wRNHfj+SSAcuX4A2mK/xvOz/ApoJJtd7nOO77azaAs2GI3N+x/oTMEpW4lsPxA1qeMA Ls1aK7Y2l6GRuLxsiY63v81tkSe8wSCaOTHHUau86sT8jU2fmCfCqvWxDHS/s4AzSch1 sX2n38gC01o2uY/EZKWMEdVGcXFG1qEv6w3DYPzIUwrg1uy7nemmJSLhJInz/2he/AIS FdyA== X-Gm-Message-State: AHYfb5hhRL7k+mqyLbp11BlKaGv6AhTv/pGHgqIS1s5IR1H/dpbBHg9Z 9VpaanqtC3p1gVOUmiOheKr+Do91mJfX X-Received: by 10.223.136.198 with SMTP id g6mr771427wrg.280.1503462670537; Tue, 22 Aug 2017 21:31:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.135.154 with HTTP; Tue, 22 Aug 2017 21:31:08 -0700 (PDT) Received: by 10.223.135.154 with HTTP; Tue, 22 Aug 2017 21:31:08 -0700 (PDT) In-Reply-To: References: <1e398f12adbdbed6b7caf3b0af07f284@bohwaz.net> <069c08bfe15b856007debab5d0d961be@bohwaz.net> Date: Wed, 23 Aug 2017 06:31:08 +0200 Message-ID: To: "BohwaZ/PHP" Cc: PHP Internals List Content-Type: multipart/alternative; boundary="001a11461b986917ad0557642eeb" Subject: Re: [PHP-DEV] Matching PDO_SQLite features with SQLite3 extension From: ocramius@gmail.com (Marco Pivetta) --001a11461b986917ad0557642eeb Content-Type: text/plain; charset="UTF-8" PDO is already a mess, and adding method that appear/disappear dynamically whether you enable an extension or not... is a horror show. From my PoV, since we (doctrine) have to abstract away from it all the time, we'd rather have it as tidy and well-thought-out as possible, especially since there already is so much damage done. Couldn't care less about exposed/unexposed features if the endpoints are on the wrong object, or cause even more weirdness to work with. It is not helpful: it's just more tech debt dumped on millions of consumers. On 23 Aug 2017 4:39 AM, "BohwaZ/PHP" wrote: > Yes, because once it lands in core, it sticks around for almost eternity. >> > > Yeah but is it necessary for something that is just missing, because the > pdo_sqlite implementation is incomplete, and is basically following what > already exists, without changing anything? > > That change was implemented in the SQLite3 extension without a RFC, so I'm > quite confused here. > > I kinda feel like it's a weird thing to submit an RFC that would basically > ask the question "should pdo_sqlite only implement a subset of SQLite", > because well it is most likely that if you are using a DB driver with PDO > you most likely want to be able to access that DB features, no? > > Or are you saying that we should have a vote on whether the implementation > should follow what is already existing in PDO or should propose something > new instead? Because I frankly don't know what would be a better idea than > driver-specific methods and I don't know enough C/have enough time to do > anything else, so I won't submit any proposition that I won't be able to do > myself. > > Cheers. > --001a11461b986917ad0557642eeb--