> On Jul 31, 2017, at 6:33 PM, Johannes Schlüter <johan...@schlueters.de> wrote: > > (off-list as this is distracting the discussion) > > On Mo, 2017-07-31 at 18:00 +0300, Andrew Nester wrote: >> >>> On Jul 31, 2017, at 5:54 PM, Johannes Schlüter <johannes@schlueters >>> .de> wrote: >>> >>> On Mo, 2017-07-31 at 14:49 +0300, Andrew Nester wrote: >>>> That’s actually the thing that you can’t use >>>> PDO::ATTR_STATEMENT_CLASS with persistent PDO. >>> The actually question is: Why not? - From 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’t work with persistent PDO connect and raises >> "General error: PDO::ATTR_STATEMENT_CLASS cannot be used with >> persistent PDO instances" > > 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 ... > > johannes
I am thinking about writing an RFC for this and continue discussion there. Will it be a good idea?
