php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #10901 mssql.min_error_severity or mssql.min_message_severity have no effect
Submitted: 2001-05-16 09:27 UTC Modified: 2001-07-02 08:32 UTC
From: mike at newfangled dot com Assigned:
Status: Closed Package: MSSQL related
PHP Version: 4.0.5 OS: Win2k Server SP1
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
21 + 43 = ?
Subscribe to this entry?

 
 [2001-05-16 09:27 UTC] mike at newfangled dot 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.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-06-30 15:16 UTC] 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-07-02 08:32 UTC] mike at newfangled dot com 
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.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Apr 20 04:01:28 2024 UTC