I have been writing tests for the spl extension and would like to submit them.
Having asked in php.qa I have been advised to ask for an svn account.
I already have some tests in svn through the testfest svn repositories however
I am no longer able to commit via that particular route.
--
PHP
On Tue, 15 Jun 2010, Ben Longden wrote:
I have been writing tests for the spl extension and would like to
submit them. Having asked in php.qa I have been advised to ask for an
svn account.
I've given you */tests karma, but please send the first few patches past
php.qa before you commit
Pierre,
That is not your decision, since when do you decide what goes into PDO,
that's a decision between the extension maintainer and the release master
and since you are neither...
On Mon, Jun 14, 2010 at 12:06 PM, Pierre Joye pierre@gmail.com wrote:
On Sat, Jun 12, 2010 at 12:24 PM,
I'll adjust the code to simply use in_txn flag for the moment to avoid the
structure change.
2010/6/14 Johannes Schlüter johan...@schlueters.de
On Thu, 2010-06-10 at 12:11 +, Ilia Alshanetsky wrote:
Modified: php/php-src/branches/PHP_5_3/ext/pdo/php_pdo_driver.h
After speaking to a few developers in DPC, I think it makes sense for us to
drop the Sqlite2 extensions from Trunk as they are superseded by the Sqlite3
extensions. The sqlite2 library is no longer maintainer and the migration
path from version 2 to 3 is very simple. Unless there any objections,
On 15 June 2010 19:41, Ilia Alshanetsky i...@prohost.org wrote:
After speaking to a few developers in DPC, I think it makes sense for us to
drop the Sqlite2 extensions from Trunk as they are superseded by the Sqlite3
extensions. The sqlite2 library is no longer maintainer and the migration
Just to clarify, removal does not mean deletion, it would simply become a
PECL extension people who need it can still use.
On Tue, Jun 15, 2010 at 9:30 AM, Adam Harvey ahar...@php.net wrote:
On 15 June 2010 19:41, Ilia Alshanetsky i...@prohost.org wrote:
After speaking to a few developers in
On 15/06/10 10:28, Derick Rethans wrote:
I've given you */tests karma, but please send the first few patches past
php.qa before you commit them.
Done, and commited. Thanks for sorting this for me!
Ben
--
http://nocarrier.co.uk
twitter: @blongden
--
PHP Internals - PHP Runtime Development
What about doing the same with MySQL extensions ?
Currently there is 3 main ways to access a MySQL server:
ext/mysql
ext/mysqli
PDO_MYSQL
Additionally, mysqlnd has to be considered as a possible library for
each of them.
I have the feeling that there is a benefit at removing ext/mysql with
the
2010/6/15 Patrick ALLAERT patrick.alla...@gmail.com:
What about doing the same with MySQL extensions ?
I have the feeling that there is a benefit at removing ext/mysql with
the same arguments as for sqlite 2.
+1 for removing ext/mysql and ext/sqlite. While we are at it, then I
think we should
On 6/15/2010 11:45 AM, Kalle Sommer Nielsen wrote:
2010/6/15 Patrick ALLAERTpatrick.alla...@gmail.com:
What about doing the same with MySQL extensions ?
I have the feeling that there is a benefit at removing ext/mysql with
the same arguments as for sqlite 2.
+1 for removing ext/mysql and
2010/6/15 Elizabeth M Smith auroraeosr...@gmail.com:
I'd have to disagree with this for one reason - it currently is the ONLY way
to speak to Sql Server on non-windows machines. Until there is an
alternative it probably needs to stay...
So only freetds works when you want to talk to mssql on
On Tue, 2010-06-15 at 07:41 -0400, Ilia Alshanetsky wrote:
After speaking to a few developers in DPC, I think it makes sense for us to
drop the Sqlite2 extensions from Trunk as they are superseded by the Sqlite3
extensions. The sqlite2 library is no longer maintainer and the migration
path
On Tue, 2010-06-15 at 16:56 +0200, Patrick ALLAERT wrote:
What about doing the same with MySQL extensions ?
Currently there is 3 main ways to access a MySQL server:
ext/mysql
ext/mysqli
PDO_MYSQL
Additionally, mysqlnd has to be considered as a possible library for
each of them.
I
There is way too much code that uses ext/mysql and ext/mysql does not depend
on a legacy library, I don't think we can remove it. As far as mssql, it is
the one way to talk to Microsoft SQL from *nix systems, until there are good
alternatives for a direct interface, I don't think we should remove
hi Ilia,
On Tue, Jun 15, 2010 at 1:41 PM, Ilia Alshanetsky i...@prohost.org wrote:
After speaking to a few developers in DPC, I think it makes sense for us to
drop the Sqlite2 extensions from Trunk as they are superseded by the Sqlite3
extensions. The sqlite2 library is no longer maintainer
Ilia Alshanetsky wrote:
There is way too much code that uses ext/mysql and ext/mysql does not depend
on a legacy library, I don't think we can remove it. As far as mssql, it is
the one way to talk to Microsoft SQL from *nix systems, until there are good
alternatives for a direct interface, I
On Tue, Jun 15, 2010 at 9:00 PM, Ryan Panning rpann...@gmail.com wrote:
Ilia Alshanetsky wrote:
There is way too much code that uses ext/mysql and ext/mysql does not
depend
on a legacy library, I don't think we can remove it. As far as mssql, it
is
the one way to talk to Microsoft SQL from
Ferenc Kovacs wrote:
I don't see any mentions about non windows enviroment.
Tyrael
I thought the ODBTP one was for Unix too. Not sure on other OS's though.
Nor other details, we use MySQL instead, just noticed this documentation.
On Tue, Jun 15, 2010 at 9:26 PM, Ryan Panning rpann...@gmail.com wrote:
Ferenc Kovacs wrote:
I don't see any mentions about non windows enviroment.
Tyrael
I thought the ODBTP one was for Unix too. Not sure on other OS's though.
Nor other details, we use MySQL instead, just noticed this
2010/6/15 Ilia Alshanetsky i...@prohost.org:
There is way too much code that uses ext/mysql and ext/mysql does not depend
on a legacy library, I don't think we can remove it. As far as mssql, it is
the one way to talk to Microsoft SQL from *nix systems, until there are good
alternatives for a
21 matches
Mail list logo
