0004979: /history doesn't skim results per-instance

ID	Project	Category	View Status	Date Submitted	Last Update
0004979	Taler	merchant backend	public	2017-03-30 10:12	2017-03-30 13:59

Reporter	Marcello Stanisci	Assigned To	Marcello Stanisci	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	no change required

Summary	0004979: /history doesn't skim results per-instance
Description	Right now, calling this API like /history?instance=FSF&start=2delta=7 returns all entries related to instance FSF, ranging 2 to 7 from all other instances. Instead, it should first retrieve all FSF's entries, and then take results from 2nd to 7th.
Tags	No tags attached.

Date Modified	Username	Field	Change
2017-03-30 10:12	Marcello Stanisci	New Issue
2017-03-30 10:12	Marcello Stanisci	Status	new => assigned
2017-03-30 10:12	Marcello Stanisci	Assigned To	=> Marcello Stanisci
2017-03-30 10:20	Marcello Stanisci	Note Added: 0011999
2017-03-30 13:59	Marcello Stanisci	Status	assigned => closed
2017-03-30 13:59	Marcello Stanisci	Resolution	open => no change required
2017-03-30 13:59	Marcello Stanisci	Note Added: 0012000
2025-03-22 13:09	Christian Grothoff	Category	mechant backend => merchant backend

Marcello Stanisci 2017-03-30 10:20 reporter ~0011999	Do you have some idea/SQL pseudocode for this? Googling seems a big waste of time/energy. Thanks.

Marcello Stanisci 2017-03-30 13:59 reporter ~0012000	Sorry, wrong report, the code already does that. It has to be extended by allowing queries "in the future" (= returning entries younger than a given point in the time), but that is a different issue.