Anonymous | Login | Signup for a new account | 09-07-2024 16:49 PDT |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0003133 | [Quercus] | minor | always | 12-07-08 00:10 | 01-04-09 14:42 | |||||||
Reporter | koreth | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | urgent | Resolution | open | Platform | ||||||||
Status | new | OS | ||||||||||
Projection | none | OS Version | ||||||||||
ETA | none | Fixed in Version | Product Version | 3.2.1 | ||||||||
Product Build | ||||||||||||
Summary | 0003133: mysql_query treats MySQL warnings as failures | |||||||||||
Description |
If MySQL responds to a query with a warning, the vanilla PHP interpreter will still return results. Quercus seems to not distinguish between warning and error responses from MySQL. Since this is a DB thing it's kind of hard to paste in a simple test case; my real-world case is an INSERT ... ON DUPLICATE KEY UPDATE on a table where one of the columns is NOT NULL but has no default value. The row in question already exists and has a value in that column (so the update succeeds) but the column isn't listed in the initial part of the INSERT clause (and thus generates MySQL warning 1364, "Field 'X' doesn't have a default value.") This query, though it's arguably broken, works in vanilla PHP but in Quercus, mysql_queryf() returns false. |
|||||||||||
Steps To Reproduce | ||||||||||||
Additional Information | ||||||||||||
Attached Files | ||||||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
32 total queries executed. 28 unique queries executed. |