Anonymous | Login | Signup for a new account | 2024-04-23 14:18 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Dependency Graph | [ View Issue ] [ Relation Graph ] [ Horizontal ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0000953 | [In-Portal CMS] Database | bug report | always | 2010-12-14 10:20 | 2011-03-30 09:53 |
Reporter | alex | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | fixed | ||
Status | closed | ||||
Summary | 0000953: Incorrect database query error reporting | ||||
Description |
In-Portal has kDBConnection class, that can handle any type of database interactions. When database query being executed produces an error, then it's handled differently based on criteria listed below: debug mode enabled AND DBG_SQL_FAILURE option set in debug.php file - will be PHP fatal error and script stops debug mode enabled AND DBG_SQL_FAILURE option not set in debug.php file - will be PHP warning and script continues to execute debug mode is disabled - will be PHP warning and script continues to execute All works ok, until you need to check if last database query ended with error in last 2 cases from above mentioned. Class kDBConnection has "getErrorCode", "getErrorMsg" and "hasError" methods, that do the trick, but if there was a query with error before checked query, then error isn't cleared an all methods will tell, that there is an error, but there are none. I propose to reset "last remembered error information" before running new database query. |
||||
Additional Information |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |