Hello all,

 

I was hoping I could get some advice on bug #44643
(http://bugs.php.net/bug.php?id=44643), where queries with bound
parameters made with the PDO ODBC driver do not have the correct type,
causing SQL errors in MSSQL (we're seeing this through the Doctrine
ORM). 

 

I've read through the notes at
http://wiki.php.net/internals/pdo/brainstorming#pdo_binding_behaviour_5.
3 and it seems that at the moment the PDO ODBC driver converts all
parameters to strings. The RFC on that page suggests changes to ensure
the type of each parameter is dependent on its zval. Have those changes
been applied? Do they relate to this bug?

 

There is also this bug report
(https://connect.microsoft.com/SQLServer/feedback/details/521409/odbc-cl
ient-mssql-does-not-work-with-bound-parameters-in-subquery) on Microsoft
Connect that suggests the issue goes beyond the PDO layer and is in
their ODBC driver instead, since the same behaviour is seen when using
the SQL Server Driver for PHP.

 

I'd be grateful for any advice regarding this matter, since I have
little knowledge of PDO. If the problem is with the ODBC PDO driver we'd
be happy to try to work up a patch for it - if it goes beyond PHP how
can I take the issue further?

 

Thanks,

Craig

 

-------------------------------------- 
Craig Marvelley

Box UK
Internet Development and Consultancy
 
t:  +44 (0) 292 022 8822
f:  +44 (0) 292 022 8820
e: craig.marvel...@boxuk.com
w:  http://www.boxuk.com <http://www.boxuk.com>    
 
Eight years in the making and more investment in usability than any
other Content Management System.  Visit http://www.amaxus.com
<http://www.amaxus.com/>  and find out why hundreds of websites are
powered by Amaxus. 

Registered Office Address: 6a Poland Street, London, W1F 8PT. Registered
in England and Wales No. 3606919.
 
Important Information: This message may contain confidential,
proprietary or privileged information. If you are not the intended
recipient, please notify the sender immediately and delete the message
from your system. You should not copy or use it for any purpose, nor
disclose its contents to any other person.

 

Reply via email to