Bug 8277 - (int-153676) CCalendar::getComponents() with iLimit/iOffset fails to retrieve recurring events
(int-153676)
: CCalendar::getComponents() with iLimit/iOffset fails to retrieve recurring ev...
Status: UNCONFIRMED
Product: Calendar
General
: 5.0/(2.2009.51-1)
: All Maemo
: Unspecified major (vote)
: ---
Assigned To: unassigned
: calendar-general-bugs
:
:
:
:
  Show dependency tree
 
Reported: 2010-01-19 17:36 UTC by Ove Kaaven
Modified: 2010-07-21 14:24 UTC (History)
3 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Ove Kaaven (reporter) 2010-01-19 17:36:35 UTC
SOFTWARE VERSION:
2.2009.51-1, also in similarly updated Scratchbox

EXACT STEPS LEADING TO PROBLEM: 
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
1. Enter some normal and some recurring events in the calendar
2. Make a test program that reads events with cal->getComponents(EVENT, -1, -1,
limit, ofs, err); (start with ofs=0, limit=100 or whatever)
3. Make a test program that reads events with cal->getComponents(EVENT, -1, -1,
err);
4. Compare
5. For extra fun, also run step 2 in a loop that increases ofs for each
iteration (until no entries are returned, of course); if you increase ofs by
the number of components returned by the previous call (as opposed to by the
limit), some events may, counterintuitively, be returned in more than one call

EXPECTED OUTCOME:
The two test programs should produce identical results (as long as the limit is
larger than the number of components in the database)

ACTUAL OUTCOME:
The first test program does not return recurring events, but the second program
does. This must be a regression, as my programs worked properly under PR1.0,
but after the upgrade, stuff vanished.

REPRODUCIBILITY:
Always (I think)

OTHER COMMENTS:
I didn't attach my own test program because it's kinda big and complex, but I
could probably make something for attachment here if you don't already have
your own test suites.
Comment 1 Andre Klapper maemo.org 2010-01-19 18:52:43 UTC
Thanks for reporting this.
Testcases are always welcome of course. :)
Comment 2 Venomrush 2010-03-23 23:35:06 UTC
Is this still reproducible with the PR1.2 scratchbox? (Nokia has just released
the Maemo 5 SDK 1.2)
Comment 3 Ove Kaaven (reporter) 2010-07-21 14:24:52 UTC
Yes, it seems the bug is still present in PR1.2 Scratchbox.