http://pear.php.net/bugs/search.php?cmd=display&package_name%5B0%5D=MDB2_Driver_odbc Search Results en-us pear-webmaster@lists.php.net pear-webmaster@lists.php.net hourly 1 2000-01-01T12:00+00:00 http://pear.php.net/gifs/pearsmall.gif http://pear.php.net/bugs http://pear.php.net/bugs/21147 MDB2_Driver_odbc Bug Reported by christian_gfk 2016-11-08T11:51:32+00:00 PHP: Irrelevant OS: RHEL 6.6 Package Version: 0.2.0 Description: ------------ The function to get error information uses a feature specific to Microsoft SQL Server: "SELECT @@ERROR". This is not supported on other RDBMS, and leads to every session run through MDB2_driver_odbc to eventually run into an error because "SELECT @@ERROR" is not a valid SQL statement for them. Expected result: ---------------- I don't know if a more generic solution exists (is PHP's odbc_error() appropriate? odbc_errormsg() is already being used). If one is available, it should be used instead. Otherwise the implicit "SELECT @@ERROR" statement should be removed.]]> MDB2_Driver_odbc Bug Reported by christian_gfk 2016-11-08T11:51:32+00:00 PHP: Irrelevant OS: RHEL 6.6 Package Version: 0.2.0 Description: ------------ The function to get error information uses a feature specific to Microsoft SQL Server: "SELECT @@ERROR". This is not supported on other RDBMS, and leads to every session run through MDB2_driver_odbc to eventually run into an error because "SELECT @@ERROR" is not a valid SQL statement for them. Expected result: ---------------- I don't know if a more generic solution exists (is PHP's odbc_error() appropriate? odbc_errormsg() is already being used). If one is available, it should be used instead. Otherwise the implicit "SELECT @@ERROR" statement should be removed.]]> 2016-11-08T11:51:32+00:00 christian dot wiese at gfk dot com MDB2_Driver_odbc Bug