Anonymous | Login | Signup for a new account | 2024-04-18 00:04 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 |
0001002 | [In-Portal CMS] Database | bug report | always | 2011-02-14 11:59 | 2011-03-30 09:53 |
Reporter | alex | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | fixed | ||
Status | closed | ||||
Summary | 0001002: Process critical database errors even when debug mode is off | ||||
Description |
If any error will happen during database query execution, then: * in debug mode: fatal error will be raised and script execution stops * in non-debug mode: warning is raised and script continues to execute It works pretty well actually, since (as we thought before) no MySQL error could be important enough to stop script execution for regular users (not developers). We was wrong actually, since these errors require reconnecting to MySQL server to fix them: * #2006 - MySQL server has gone away * #2013 - Lost connection to MySQL server during query In case on of these errors will happen during database query execution, then we should: 1. disconnect and connect to MySQL again 2. try to run database query that raised an error 3. do 3 retries and if we still got an error, then - act the same as before OR - die? |
||||
Additional Information |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |