| Anonymous | Login | Signup for a new account | 04-18-2024 03:09 PDT |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| 0003300 | [Quercus] | minor | always | 01-28-09 05:01 | 01-28-09 08:02 | |||||||
| Reporter | tolmi | View Status | public | |||||||||
| Assigned To | ||||||||||||
| Priority | normal | Resolution | open | |||||||||
| Status | new | Product Version | 3.2.1 | |||||||||
| Summary | 0003300: mysqli_errno returns 0 when error happened | |||||||||||
| Description |
mysql_errno and mysqli_errno should return a non-zero value when something went wrong on the last time a mysql function was used. This turned out while running Drupal on Quercus and the database went offline. Drupal checks mysqli_errno() to be bigger than zero. Attached a patch to fix the issue. |
|||||||||||
| Additional Information | ||||||||||||
| Attached Files |
 mysqli_errno_fix.patch [^] (1,128 bytes) 01-28-09 05:01 |
|||||||||||
|
|
||||||||||||
 Relationships |
|
|
Notes |
|
|
(0003782) tolmi 01-28-09 08:02 |
I re-read my description and the errno functions are incorrect. mysql_errno() in this case irrelevant, and mysqli_errno should not be used to check if the connection had any errors. Instead the mysqli_connect_errno() should be used. Of course the problem still exists, the patch fixes it anyway I just wanted to clarify. |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 01-28-09 05:01 | tolmi | New Issue | |
| 01-28-09 05:01 | tolmi | File Added: mysqli_errno_fix.patch | |
| 01-28-09 08:02 | tolmi | Note Added: 0003782 | |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 25 unique queries executed. |  |
