Date: 02/29/00
- Next message: Bug Database: "[PHP-DEV] Bug #3102 Updated: Buffer overflow with rfc822_date"
- Previous message: Bug Database: "[PHP-DEV] Bug #3464 Updated: imap_fetchstructure incompatible behavior"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
From: moregan <email protected>
Operating system: NT4WS SP6a
PHP version: 4.0 Beta 4 Patch Level 1
PHP Bug Type: ODBC related
Bug description: odbc_execute() reports failure for SQL_SUCCESS_WITH_INFO
odbc_exec() and odbc_execute() return the failure condition if the statement being executed returns SQL_SUCCESS_WITH_INFO from the driver, which is not what I would expect. E.g. the Microsoft SQL Server driver hitting an MSDE database with the statement odbc_exec( "USE MARC" ) returns SQL_SUCCESS_WITH_INFO, the message being basically "OK, I changed databases". With odbc_exec() the return is false. With odbc_execute() the return is false and the output page reports that the statement failed.
In php_odbc.c, odbc_execute() checks ( rc != SQL_SUCCESS ) with the return from SQLExecute(), which could be it. Most--curiously not all--error code tests also check for SQL_SUCCESS_WITH_INFO in this module.
I didn't try PHP3, but the 3.0.15 source also has (rc!=SQL_SUCCESS). Does the fact that such code is in production imply that there's instead something wrong with the driver? (The only thing I can think of would be that SQL_SUCCESS_WITH_INFO might not be allowed from SQLExecute(), but I don't have the spec handy to check.)
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Bug Database: "[PHP-DEV] Bug #3102 Updated: Buffer overflow with rfc822_date"
- Previous message: Bug Database: "[PHP-DEV] Bug #3464 Updated: imap_fetchstructure incompatible behavior"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

