On Wed, 2017-03-22 at 19:51 +0100, Jan Sedlak wrote:
As I understand it, if you'd ask for "latest test with item
== X", it
would just go through the database sorted by the time and returned on
first item with "item == X" it would find. But, if you'd ask for
"latest tests with item == X for each unique value 'scenario'", it
would not stop on the first item with "item == X", it would have to go
through the whole DB, because what if there is some other item with
"item == X" but different scenario value? You would have to create a
new table with all possible "scenario" values, but that wouldn't be a
generic solution.
I guess the usage I was kinda assuming was that you'd request 'all
tests with item == X' and then do the scenario de-duplication on the
client side. This is what Bodhi does now, for instance - it just kinda
invents the scenario concept on its end. It doesn't just ask for 'the
latest result for item X' from rdb.
Is asking for 'all results for item == X' gonna be too much work for
rdb to handle? Is that the problem?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net