Bug #50444 [Opn->Csd]: PDO-ODBC changes for 64-bit

Edit report at https://bugs.php.net/bug.php?id=50444&edit=1 ID: 50444 Updated by: stas@php.net Reported by: davbrown4 at yahoo dot com Summary: PDO-ODBC changes for 64-bit -Status: Open +Status: Closed Type: Bug Package: PDO ODBC Operating System: Solaris PHP Version: 5.3.1 Block user comment: N Private report: N New Comment: Automatic comment on behalf of kehrigan@gmail.com Revision: http://git.php.net/?p=php-src.git;a=commit;h=186ffcb72c982b0235761bdd6388ff1c36d79568 Log: Fix #50444: PDO-ODBC changes for 64-bit Previous Comments: ------------------------------------------------------------------------ [2014-03-28 16:03:21] fdemoures at sotraig dot fr I use pdo_odbc on Ubuntu 13.10 x86_64 with php 5.5.3 and the new driver odbc IBM i Access. Segmentation fault occurs on execute() after a prepare(). If I use query() directly, it works. On architecture i386 it works. ------------------------------------------------------------------------ [2014-03-19 23:21:12] kadler at us dot ibm dot com We have customers running in to this problem on x86_64 and PPC64 Linux using our new IBM i Access ODBC driver, since we now build against the newer version of unixODBC that has a 64-bit SQLLEN. I've added a pull request against the latest code in GitHub. Hopefully, this should make it easy enough to close this nearly 4.5 year old bug. ------------------------------------------------------------------------ [2014-01-31 19:13:09] samifruit514 at hotmail dot com We also need this for our sql server native 11 connection ------------------------------------------------------------------------ [2013-01-30 00:43:04] paul dot posts at gmail dot com Related To: Bug #61777 ------------------------------------------------------------------------ [2011-10-12 16:59:20] davbrown4 at yahoo dot com Hello - are there any plans to accept this fix? We have customers using php who need this fix. ------------------------------------------------------------------------ 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=50444 -- Edit this bug report at https://bugs.php.net/bug.php?id=50444&edit=1