Howdy,
I've been trying to find someone who could help me with a fix for a few bugs
in PDO_ODBC, and had no luck so far. I am more than happy to compensate
someone for the time spent fixing these bugs.
One is bug #36561
(http://bugs.php.net/bug.php?id=36561http://bugs.php.net/bug.php?id=36561&thanks=2)
[PDO_ODBC/MSSQL does not work with bound params in subquery]
Another is a bug where long nvarchar (>126 characters) or ntext fields in a
select statement get an EOS character in the middle. This one was fixed for
me by Wez, but I don't think the change ever made it into the CVS, so I'm
stuck on 5.1.3 with a special patch for that bug.
There is a third one with long fields in a select statement not returning
unless they are the last fields selected, but I think that one is fixed in
the latest versions of php.
If anyone would be willing to help fix these and get them in the cvs, please
let me know. I've been working around these bugs for a couple of years now,
and really want to upgrade my php version and remove the silly workarounds
I've been forced to implement!
If this is inappropriate here, I apologize... I just don't know where else
to go. I've tried contacting several folks individually but no-one has
seemed interested.
Thanks,
--Travis
I've been trying to find someone who could help me with a fix for a few bugs
in PDO_ODBC, and had no luck so far. I am more than happy to compensate
someone for the time spent fixing these bugs.
Unfortunately it is not that easy as it seems. For some reason the
pecl/pdo_odbc and php-src/ext/pdo_odb directories are locked out for
the "normal" PHP team and thus we can't commit to it. The comment in the
rights file says:
DB2, SDO, IDS have tighter restrictions, so that IBM are not overly
legally encumbered. If you have contributions for these two extensions,
please contact the lead developers. This is a temporary measure until
we can put in place a more general process.
It has been in this temporary situation since June 2005 :-/
regards,
Derick
--
Derick Rethans
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
PDO_ODBC is not the base which IBM is maintaining (theirs is PDO_IBM). They are usually very responsive to issues (at least in my experience).
Looks like currently Wez is maintainer for PDO_ODBC.
Andi
-----Original Message-----
From: Derick Rethans [mailto:derick@php.net]
Sent: Tuesday, December 18, 2007 7:54 AM
To: Travis Raybold
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Will pay for fixes for bugs in PDO/PDO_ODBCI've been trying to find someone who could help me with a fix for a
few bugs
in PDO_ODBC, and had no luck so far. I am more than happy to
compensate
someone for the time spent fixing these bugs.Unfortunately it is not that easy as it seems. For some reason the
pecl/pdo_odbc and php-src/ext/pdo_odb directories are locked out for
the "normal" PHP team and thus we can't commit to it. The comment in
the
rights file says:DB2, SDO, IDS have tighter restrictions, so that IBM are not overly
legally encumbered. If you have contributions for these two
extensions,
please contact the lead developers. This is a temporary measure
until
we can put in place a more general process.
It has been in this temporary situation since June 2005 :-/
regards,
Derick--
Derick Rethans
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
Derick,
Your statement is not accurate:
http://cvs.php.net/viewvc.cgi/CVSROOT/avail?r1=1.1200&r2=1.1201
This should not be a blocker to anyone that wants to take this up.
I've been too busy to help Travis (I'm really sorry about that
Travis), and I'm happy to share the pending fix with anyone that wants
to look at this.
The reason that the code hasn't gone into CVS is that Travis had a
knack for picking a tree freeze for bringing up his issues, and then I
would subsequently become too busy to get the code sync'd up after the
freeze.
Anyhow, if anyone does want to take Travis up on his offer, you'll
need the attached patch.
Your statement is not accurate:
http://cvs.php.net/viewvc.cgi/CVSROOT/avail?r1=1.1200&r2=1.1201This should not be a blocker to anyone that wants to take this up.
Missed that it was "removed" already. However, having a "restriction" in
the first round does make people lose interest in specific bits of
extensions - this is also why I am against any sort of restriction of
committing on any bit of code inside the PHP core distribution.
Anyhow, if anyone does want to take Travis up on his offer, you'll need the
attached patch.
JFYI: Mail.app is broken, please add attachments as attachments instead
of "dragging" it in - it splits a normal mail up in two, so I almost
missed this part:
PS: More on PDO soon; it has not been forgotten despite sickness, work
and so forth.
Things like that happen, but it would have been much more proper to
bring those things up before actually implementing something that many
seem to be quite everse against.
regards,
Derick
--
Derick Rethans
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
Would someone be willing to apply the patch the Wez emailed in? That would
at least enable me to upgrade to the latest version of php once it is in a
released version.
I'd still love to get a fix for bug #36561 [PDO_ODBC/MSSQL does not work
with bound params in subquery], anyone interested? Name a price, hourly
rate, whatever, as long as I still get to keep my firstborn... ;)
--Travis
Derick,
Your statement is not accurate:
http://cvs.php.net/viewvc.cgi/CVSROOT/avail?r1=1.1200&r2=1.1201This should not be a blocker to anyone that wants to take this up.
I've been too busy to help Travis (I'm really sorry about that
Travis), and I'm happy to share the pending fix with anyone that wants
to look at this.The reason that the code hasn't gone into CVS is that Travis had a
knack for picking a tree freeze for bringing up his issues, and then I
would subsequently become too busy to get the code sync'd up after the
freeze.Anyhow, if anyone does want to take Travis up on his offer, you'll
need the attached patch.--Wez.
PS: More on PDO soon; it has not been forgotten despite sickness, work
and so forth.I've been trying to find someone who could help me with a fix for a
few bugs
in PDO_ODBC, and had no luck so far. I am more than happy to
compensate
someone for the time spent fixing these bugs.Unfortunately it is not that easy as it seems. For some reason the
pecl/pdo_odbc and php-src/ext/pdo_odb directories are locked out for
the "normal" PHP team and thus we can't commit to it. The comment in
the
rights file says:DB2, SDO, IDS have tighter restrictions, so that IBM are not overly
legally encumbered. If you have contributions for these two
extensions,
please contact the lead developers. This is a temporary measure
until
we can put in place a more general process.
It has been in this temporary situation since June 2005 :-/
regards,
Derick--
Derick Rethans
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org