Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100154
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain bk.ru designates 94.100.177.99 as permitted sender)
Message-ID: <B11F0039-0508-43B3-9873-E99AA58F12F1@bk.ru>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_36C74E2B-55AB-40DA-9F0C-84C29CE5CD2E"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 3 Aug 2017 19:59:05 +0300
In-Reply-To: <1501515189.14647.35.camel@schlueters.de>
Cc: internals@lists.php.net
To: =?utf-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
References: <1907EFF3-ED77-4F5C-85AA-CDFE323369C5@bk.ru>
 <CA+kxMuRXTxxsWyHumtGiyjU+pQ_KSTbtiNMd-V+U9YKPgxCNyA@mail.gmail.com>
 <880CDC06-17D6-4E40-8A48-F2E1CB405667@bk.ru>
 <CA+kxMuRXnUrnhqQQW9pj--UY8eSQoOrZriMUioG5Th_-8HmYqg@mail.gmail.com>
 <2A653728-97CA-4AA5-BA30-5BF26FABBC2A@bk.ru>
 <1501512881.14647.31.camel@schlueters.de>
 <94973CB5-A3F8-4BE4-9A78-8F759D1829E7@bk.ru>
 <1501515189.14647.35.camel@schlueters.de>
Subject: Re: [PHP-DEV] [Request][Discussion] Introduce interfaces PDOInterface
 and PDOStatementInterface
From: newaltgroup@bk.ru (Andrew Nester)

--Apple-Mail=_36C74E2B-55AB-40DA-9F0C-84C29CE5CD2E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Jul 31, 2017, at 6:33 PM, Johannes Schl=C3=BCter =
<johannes@schlueters.de> wrote:
>=20
> (off-list as this is distracting the discussion)
>=20
> On Mo, 2017-07-31 at 18:00 +0300, Andrew Nester wrote:
>>=20
>>> On Jul 31, 2017, at 5:54 PM, Johannes Schl=C3=BCter =
<johannes@schlueters
>>> .de> wrote:
>>>=20
>>> On Mo, 2017-07-31 at 14:49 +0300, Andrew Nester wrote:
>>>> That=E2=80=99s actually the thing that you can=E2=80=99t use
>>>> PDO::ATTR_STATEMENT_CLASS with persistent PDO.
>>> The actually question is: Why not? - =46rom a quick glance on the
>>> code I see no obvious reason
> [...]
>> Besides code style/architecture things (which is of course
>> questionable) the issue with ATTR_STATEMENT_CLASS is that it simply
>> doesn=E2=80=99t work with persistent PDO connect and raises=20
>> "General error: PDO::ATTR_STATEMENT_CLASS cannot be used with
>> persistent PDO instances"
>=20
> Yes, and my question is "why can't it?" I see no obvious reason in the
> code. If we can lift weird restrictions from internals this is always
> good ...=20
>=20
> johannes

I am thinking about writing an RFC for this and continue discussion =
there.
Will it be a good idea?


--Apple-Mail=_36C74E2B-55AB-40DA-9F0C-84C29CE5CD2E--