get_record_sql() breaks when the SQL contains a LIMIT
Bug #716533 reported by
Matt Oquist
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mahara |
Fix Released
|
Low
|
François Marier | ||
Bug Description
It would be nice if get_record_sql() allowed queries that use ORDER BY and LIMIT 1 to ensure that the desired record is returned. Currently, queries with LIMIT break get_record_sql().
I tested a fresh installation of 1.4.0alpha2dev with this patch and everything seemed to be fine.
Revision history for this message
| Matt Oquist (moquist) wrote | #1 |
Revision history for this message
| François Marier (fmarier) wrote | #2 |
| Changed in mahara: | |
| milestone: | none → 1.4.0 |
| assignee: | nobody → François Marier (fmarier) |
| importance: | Undecided → Low |
| status: | New → Fix Committed |
| Changed in mahara: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Looks good to me. Thanks Matt!
I've run the Selenium tests and they are just as broken with and without that patch, so that's as good as it gets :)