Ticket #19 (defect)
Opened 5 years ago
Last modified 4 years ago
Support imperfect SQL when LIMIT/OFFSET is provided
Status: closed (fixed)
| Reported by: | fumanchu | Assigned to: | fumanchu |
|---|---|---|---|
| Priority: | major | Milestone: | 1.0 |
| Component: | SQL | Version: | |
| Keywords: | Cc: | ||
| Estimate (total hours): | 8 |
I noticed this in a MySQL test when trying to retrieve a row by one of its float columns: lambda x: x.Admission == float(60). Since MySQL has no reliable means of comparing floats, this gets punted back to Python by writing "SELECT ... FROM Zoo WHERE TRUE". But, for example, if LIMIT 1 were also provided, Database.select doesn't try to retrieve more than the 1 row, which has a low probability of being the row we want.
Change History
11/18/07 17:46:25: Modified by fumanchu
- status changed from new to assigned.
04/04/08 03:11:39: Modified by fumanchu
- status changed from assigned to closed.
- resolution set to fixed.
Test and temporary "fix" (raise an error) in [238].