Opened 9 years ago

Closed 7 years ago

#12516 closed Bug Report - General (Fixed)

GetRecodedList API call - inconsistent StartIndex

Reported by: Phil Brady <phil.brady@…> Owned by: Bill Meek
Priority: minor Milestone: 0.28
Component: MythTV - General Version: 0.27.4
Severity: low Keywords: GetRecordedList, Services API, StartIndex
Cc: Ticket locked: no

Description

With the GetRecordedList? API call, StartIndex?=0 and StartIndex?=1 return the same data. Thus code which grabs the data in chunks eg

StartIndex?=0&Count=100 StartIndex?=100&Count=100

will have a duplicate returned because he first call will return 1 to 100 inclusive, the second 100 to 199. ie indexing starts at 1 not zero, unlike other calls eg GetChannelL

Change History (3)

comment:1 Changed 7 years ago by paulh

Owner: set to Bill Meek
Status: new → assigned

Bill do you want to look at this one?

comment:2 Changed 7 years ago by Bill Meek

Status: assigned → infoneeded

Phil, is this still an isssue? Consider the following: 

http://<BE>:6544/Dvr/GetRecordedList?StartIndex=0&Count=2
http://<BE>:6544/Dvr/GetRecordedList?StartIndex=1&Count=2
http://<BE>:6544/Dvr/GetRecordedList?StartIndex=2&Count=2

I get recordings (A and B), (B and C) then (C and D) respectively. That's the result I'd expect.

I also tried using StartIndex=0 and 100 with Count=100 and the result didn't have an overlap (the title of the 100th and 101st were the same, but the subtitles were different in my case.)

comment:3 Changed 7 years ago by Bill Meek

Milestone: unknown → 0.28
Resolution: → Fixed
Status: infoneeded → closed

Fixed in 0.28 with a combination of 715367fdb2a73ed4f9cb3fdaab21385f8122be7f and 66fbffa29de034e5c55d72d69c9f137626817871

Note: See TracTickets for help on using tickets.