Bug #10901 Updated: mssql.min_error_severity or mssql.min_message_severity have no effect

ID: 10901 User Update by: mike@newfangled.com Status: Closed Bug Type: MSSQL related Operating system: Win2k Server SP1 PHP Version: 4.0.5 Description: mssql.min_error_severity or mssql.min_message_severity have no effect I was checking for errors from the mssql_query() function and not from the mssql_get_last_message(). The function call failed even though I set the warning and severity levels to 11. Previous Comments: --------------------------------------------------------------------------- [2001-06-30 15:16:18] fmk@php.net Using mssql_get_last_message will allways retune the last server message. Setting mssql.min_message_severity and mssql.min_error_severity will only affect the PHP Warnings printed in your script. You should not use mssql_get_last_message to check for errors, but use the return value of the function. If a function returns FALSE, you can check mssql_get_last_message to get the message. --------------------------------------------------------------------------- [2001-05-16 09:27:14] mike@newfangled.com mssql.min_message_severity mssql.min_error_severity in the php.ini file have no effect on messages received from MSSQL. I am running MSSQL 7.0 SP2. I still get Changed database context to 'dbname'. warning on queries even after setting the above values to greater than 10. The above warning is a level 10 warning. --------------------------------------------------------------------------- Full Bug description available at: http://bugs.php.net/?id=10901