I cannot comment directly on the creation of ext/ibmdb2, although I'd
rather see something like that moved to PECL (where everything will be
eventually). As for separate CVS trees, while it sounds like a good
idea, it's my opinion that it's not a good thing.
I agree - I'll submit patches
On Fri, 08 Nov 2002 22:06:07 -0800
Frank M. Kromann [EMAIL PROTECTED] wrote:
I don't see a need to add specific db2 functions, but perhaps extend
the ODBC extension with generic ODBC/CLI functions.
I'll go that route then. I am looking at very large databases, so it is
important that the php
Hi,
I am writing php applications which use php's builtin ibm-db2 support through odbc.
However there are some DB2-specific extensions which are not included in php's DB2
support. I am interested in adding this functionality to php. Who should I talk to in
order to avoid duplication of work?
Tim,
I've been maintaining the ODBC extension for a bit. While I welcome
the addition of new ODBC functionality, I am hesitent to add in
functions that are not ODBC compliant to the code (i.e. db2_connect(),
or some such).
If you can make the functions generic enough that they can be
On Fri, 8 Nov 2002 08:18:06 -0500
Dan Kalowsky [EMAIL PROTECTED] wrote:
I've been maintaining the ODBC extension for a bit. While I welcome
the addition of new ODBC functionality, I am hesitent to add in
functions that are not ODBC compliant to the code (i.e. db2_connect(),
or some
On Friday, November 8, 2002, at 08:34 PM, tim wrote:
If I take the existing php odbc code and add the ibm-db2 specific
extensions, what are the chances of this making it into the main php
distribution as a new extension ( ext/ibmdb2 ) ? Is it a good idea to
maintain a separate cvs tree on
Hi,
To my knowledge IBM uses a Client Level Interface CLI and the
specifications for CLI is exactly the same as ODBC. Compiling the ODBC
extension with CLI and some other form of ODBC library would make sence if
you wanted to use native IBM code and other ODBC at the same time. This
was the case
