Re: Matching PDO_SQLite features with SQLite3 extension

From: Date: Wed, 23 Aug 2017 04:39:46 +0000
Subject: Re: Matching PDO_SQLite features with SQLite3 extension
References: 1 2 3 4 5 6  Groups: php.internals 
Request: Send a blank email to internals+get-100284@lists.php.net to get a copy of this message
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.
Yes I agree, but it's not the point, this behaviour already exists, I'm not introducing anything new here.
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.
I care because I need those features in my projects, and I'm not the only one. But if those late-loading methods don't suit you, what do you propose instead?

« previous php.internals (#100284) next »