Activity log for bug #301187
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2008-11-23 04:22:17 | Ray C Horn | bug | added bug | ||
| 2009-01-24 00:31:59 | Kevin Shuk | pyax: status | New | Confirmed | |
| 2009-01-24 00:31:59 | Kevin Shuk | pyax: assignee | surf | ||
| 2009-01-24 00:31:59 | Kevin Shuk | pyax: importance | Undecided | High | |
| 2009-01-24 00:31:59 | Kevin Shuk | pyax: statusexplanation | I will have to check the query itself to to see if it's a select count() and act accordingly, otherwise a legitimate query that returns no rows may provide a surprising result (not an empty batch). Borrowing behaviour from apex, the count() query should return just the integer. It's a different enough kind of query to warrant this, and since SOQL isn't SQL, I don't feel quite so bad about the different behaviour. | ||
| 2009-01-24 00:37:51 | Kevin Shuk | pyax: status | Confirmed | Fix Committed | |
| 2009-01-24 00:37:51 | Kevin Shuk | pyax: statusexplanation | I will have to check the query itself to to see if it's a select count() and act accordingly, otherwise a legitimate query that returns no rows may provide a surprising result (not an empty batch). Borrowing behaviour from apex, the count() query should return just the integer. It's a different enough kind of query to warrant this, and since SOQL isn't SQL, I don't feel quite so bad about the different behaviour. | Committed to rev 65 |
