On Thu, Jun 3, 2010 at 7:28 PM, Jonathan Wage <jonw...@gmail.com> wrote:
> Hi, > > On Thu, Jun 3, 2010 at 1:16 PM, Ferenc Kovacs <i...@tyrael.hu> wrote: > >> If that so, I would be happy to see some discussion and work on the PDO, >> because from a user perspective, it seems like abadoned. >> I think that we should allow to get things commited, because: >> 1, the trunk is a trunk, if something gets commited, it doesn't mean, that >> it will be merged for the release. >> > > Ok, that is a valid argument. But lets be real here. Chances are that if it > makes it into trunk, nobody will say anything and it will make it into the > final release. > I disagree here, but if nobody will solve this situation until the next release, then I think its better to have _something_, than chasing away people who are contributing, and waiting something to happen. > Take a look at the inconsistency of PHP as a whole and you'll see that this > is not really a good idea. If someone, somewhere commits something it can > make it into PHP and that's why PHP is in the state it is in today. > So? Now we shouldn't try to improve things because they aren't perfect? > We need to stop this and start fixing it today. > Go ahed. Do you have any timeline for it? > If you don't agree, you are in denial. The API of PHP now is proof. > > I'm agree, I'm just not seeing any progress, only excuses why should we wait for the great improvement, that should be happen anytime soon... > 2, it can start a healty discussion and brainstorming about the current >> problem, and the solution. >> >> > We're already discussing it. We don't have to commit something that is > obviously wrong in order to do that. > > Where? The last modification in the manual was in january, and the only discussion recently on php.pdo is about extending pdo with two driver specific(both are for postgresql, one of them is this that we are talking about) feature. http://news.php.net/group.php?group=php.pdo So this is why I said, that there is no progress, just holding back the people like Denis who are willing to help, making the patch, sorting out the problems, writing testcases, doing the groundwork. If there will be a better solution(like the ones what we discussed above), and somebody will actually implement that, then this feature can be reverted as well. But right now I didn't see any work in that direction. Tyrael
