On Sat, Jun 5, 2010 at 10:54 AM, Oskar Eisemuth <patch...@gmail.com> wrote:

> Pierre Joye wrote:
>
>> On Thu, Jun 3, 2010 at 8:47 PM, Ferenc Kovacs <i...@tyrael.hu> wrote:
>>
>>
>>> Agree, but currently I don't see any point in waiting, if we don't do
>>> anything else beside waiting.
>>>
>>>
>>
>> There are discussions about that on the PDO list in the past. However,
>> it is because we failed to start discussions that we should give up
>> and continue to add bad designed features to PDO, with all respects to
>> the author of the patch.
>>
>> Now let begin an open discussion to define what we actually need for
>> PHP to continue to rock the web
>>
> Well, I collected various points at
> http://wiki.php.net/internals/pdo/brainstorming  (a wiki page started by
> Lukas)

The big problem I see, there is no one to take responsible for PDO. In my
> opinion stuff that should work since ages should be fixed and then new
> features can be added in a sane and most backward compatible way. So the
> solution I use currently is to wrap PDO and try to fix the most annoying
> binding bugs in userland, but for higher level stuff that won't work.
>
> Imho, using a connection pointer for going back to the native libs is the
> wrong approach, so adding somehow the missing feature is the only right way
> for PDO.
>
> I think the discussion was already started, but as usually the pdo list
> doesn't have enough people to get things done and will be silent for the
> next "decade" as soon as the first ideas show up. I don't see a benefit in
> collecting the ideas at the wiki either as no one really cares anyway...
>
> ----
> Oskar Eisemuth
>
>
Yeah, this pretty much sums up my opinion.

Tyrael

ps:
http://en.wikipedia.org/wiki/Bikeshedding
http://en.wikipedia.org/wiki/Overengineering

Reply via email to