Edit report at https://bugs.php.net/bug.php?id=44643&edit=1
ID: 44643
Comment by: wschalle at gmail dot com
Reported by: ethan dot nelson at ltd dot org
Summary: PDO_ODBC: bound parameters ignore explicit type
definitions
Status: Open
Type: Bug
Package: PDO ODBC
Operating System: *
PHP Version: 5.2CVS-2009-03-20
Block user comment: N
Private report: N
New Comment:
As an addendum, I think pdo_sqlsrv has a very thorough implementation of type translation between
PHP and SQL types and back. It is exhaustively complete, but doesn't perform quite as well as
pdo_odbc's one-size-fits-all routine.
At least some of what pdo_sqlsrv is doing instead of calling SQLDescribeParam is an example of the
right general way to solve the issues in pdo_odbc that occur when SQLDescribeParam is not supported
or supported only partially.
Previous Comments:
------------------------------------------------------------------------
[2014-03-08 22:22:05] wschalle at gmail dot com
This isn't due to a SQL server bug but instead it is due to well-documented laziness on the sql
server developers part when writing the SQLDescribeParam function in the SQL Server ODBC driver.
Basically when parameters are within a subquery, SQLDescribeParam doesn't return data for them.
The fact that this breaks queries is actually pdo_odbc's fault though, for relying entirely on
the output (or lack thereof) of SQLDescribeParam to dictate how it then passes the PHP variable
through to the SQLBindParam function.
This issue doesn't just exist with the SQL Server driver either, there are several DBMS's
with issues with SQLDescribeParam, but sql server's behavior is the worst.
PDO's handling of a bad return from SQLDescribeParam is not quite where it should be - right
now if SQLDescribeParam doesn't work, the driver makes the strange assumption that the
parameter should be sent as either SQL_LONGVARBINARY in the case of a LOB or SQL_LONGVARCHAR in the
case of a non-LOB type.
The correct behavior would be at the very least to use the specified param_type and/or the PHP type
to make a better fallback guess. Bound parameters specified as PDO_PARAM_INT should absolutely be
cast to long and sent to the server as SQLINTEGER.
I'd really like to see this bug fixed, as it is one of the only things keeping PHP running on
linux from accessing SQL server properly. My app supports a variety of DBMS's, but if a company
has data in SQL Server and we need to access it, the app either has to run on a windows server (god
why), use non-parameterized queries, replace all parameter placeholders with CAST(CAST(?,
varchar),int), use parameterized queries without any subqueries, or use direct exec queries. Not the
best of situations.
PERL has had the same issues - see:
https://rt.cpan.org/Public/Bug/Display.html?id=64968https://rt.cpan.org/Public/Bug/Display.html?id=50852http://www.martin-evans.me.uk/node/50
------------------------------------------------------------------------
[2010-08-17 20:46:11] kraven at kraven dot org
This is caused by a long standing MS SQL ODBC Client bug. http://connect.microsoft.com/SQLServer/feedback/details/521409/odbc-client-mssql-does-not-work-with-bound-parameters-in-subquery
Last update on 8/3/2010 was that it would be resolved in a future release of the SQL Server Native
Access Client.
------------------------------------------------------------------------
[2009-05-21 21:49:40] ethan dot nelson at ltd dot org
This also happens for the new Native Client 10.0 driver for SQL 2008.
SELECT * FROM (SELECT 'test' = :id) a WHERE a.test = :id2
Array
(
[0] => 42000
[1] => 402
[2] => [Microsoft][SQL Server Native Client 10.0][SQL Server]The
data types text and text are incompatible in the equal to operator.
(SQLExecute[402] at ext\pdo_odbc\odbc_stmt.c:133)
[3] => 42000
)
PHP Version 5.2.9-2
System Windows NT LTD-PWWW2 5.2 build 3790
Build Date Apr 9 2009 08:22:37
Configure Command cscript /nologo configure.js "--enable-snapshot-
build" "--enable-debug-pack" "--with-snapshot-template=d:\php-
sdk\snap_5_2\vc6\x86\template" "--with-php-build=d:\php-
sdk\snap_5_2\vc6\x86\php_build" "--with-pdo-oci=D:\php-
sdk\oracle\instantclient10\sdk,shared" "--with-oci8=D:\php-
sdk\oracle\instantclient10\sdk,shared"
Server API ISAPI
------------------------------------------------------------------------
[2009-03-20 17:12:18] phpbugs at matthewboehm dot com
RHEL-5.3 php5.2-200903201530
Invalid character value for cast specification: 206 [FreeTDS][SQL
Server]Operand type clash: text is incompatible with int
(SQLExecute[206] at /usr/src/php5.2-
200903201530/ext/pdo_odbc/odbc_stmt.c:133
------------------------------------------------------------------------
[2008-10-28 17:37:00] ethan dot nelson at ltd dot org
<?php
ini_set("display_errors","yes");
$poo = new PDO("odbc:DEVELOPMENT");
$query = "SELECT * FROM (SELECT 'test' = :id) a WHERE a.test = :id2";
$stm = $poo->prepare($query);
echo $query."<br>\n";
$id = 1;
$stm->bindParam(':id',$id,PDO::PARAM_INT);
$id2 = 1;
$stm->bindParam(':id2',$id2,PDO::PARAM_INT);
echo "<pre>\n";
if ($stm->execute()) print_r($stm->fetchAll(PDO::FETCH_ASSOC));
else print_r( $stm->errorInfo());
echo "</pre>\n";
phpinfo();
?>
-----------The above returns the below result:
SELECT * FROM (SELECT 'test' = :id) a WHERE a.test = :id2
Array
(
[0] => 42000
[1] => 402
[2] => [Microsoft][SQL Native Client][SQL Server]The data types
text and text are incompatible in the equal to operator.
(SQLExecute[402] at ext\pdo_odbc\odbc_stmt.c:133)
[3] => 42000
)
PHP Version 5.2.7RC2-dev
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=44643--
Edit this bug report at https://bugs.php.net/bug.php?id=44643&edit=1