Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100864
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.192.180 cause and error)
MIME-Version: 1.0
In-Reply-To: <050ebe9b36b83431a4f2d5c170de57ad@bohwaz.net>
References: <b59a6f4be9a975b5f0b92fd8ad74ed58@bohwaz.net> <050ebe9b36b83431a4f2d5c170de57ad@bohwaz.net>
Date: Thu, 12 Oct 2017 00:00:28 +0100
Message-ID: <CA+kxMuSf6REJShV+BWAu6zDzb-VfrQQHMOEGOrU35WECuuBV3A@mail.gmail.com>
To: "BohwaZ/PHP" <php@bohwaz.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Implement missing SQLite feature
 "openBlob" in PDO
From: danack@basereality.com (Dan Ackroyd)

On 11 October 2017 at 22:03, BohwaZ/PHP <php@bohwaz.net> wrote:
> Hey,
>
> For people voting against the RFC, could you please explain your vote here
> so that we might understand?
>
> Cheers.

I think people were reasonably clear during the discussion.

Having certain methods only available on an object depending on how it
was initialized is just not a good idea.

Danack wrote:
> This might be a mistake in how it was implemented originally. Looking
> back it seems that it was implemented before we had the RFC
> process....and is exactly the type of 'sub-optimal' implementation the
> RFC process is meant to prevent.
>
> ...rather thank just hack in new features building on sub-optimal
> ways of doing things, I think it would be better to create a plan to
> clean up the way that connection specific methods are available, with
> something along the lines of that which I mentioned above.

Regardless of how the vote for this RFC goes, it would be appropriate
to have an RFC to clean up how PDO makes connection specific methods
available.

If the current RFC fails, I would guess that people would be happier
adding the connection specific methods in a less magic way.

cheers
Dan