I was pondering “correctness” of including minimum and maximum under “aggregates”, and concluded that whilst arguably incorrect it didn’t really matter.
Then today… it occurs to me that there could be an important difference: with min/max I need to retrieve not only the min/max value but also a sibling thereof. E.g. if a customers table has a related customerPayments table (which includes date and value) then retrieving the date of the most recent payment is simple (MAX(customers_to_customerPayments.date)) but retrieving the value of that payment doesn’t appear to be as simply done (i.e. I’m resorting to putting SQL queries in calculations).
Any chance that min/max aggregations could be moved into another tab where we can separately specify the dataprovider which is the subject of the min/max function and the dataprovider which is returned?
Or is there some relatively simple strategy which I have overlooked?
Thanks,
Neale.