On Thu, 2017-03-30 at 18:13 +0200, Josef Skladanka wrote:
On Thu, Mar 30, 2017 at 5:03 PM, Adam Williamson
<adamwill(a)fedoraproject.org
> wrote:
> On Wed, 2017-03-22 at 09:07 -0400, Kamil Paral wrote:
>
> > I know this has been a long email, but, feedback needed! :-)
>
> So I just read through this again.
>
> I'm wondering if we can do something simpler and within resultsdb,
> though it still *is* adding complexity: basically, add de-duplication
> by specified fields as a feature to resultsdb
>
Sure, can be done. It is not "simple" though, and still requires traversing
all the data in database, plus it means more CPU and memory load on the web
server (as it will be doing the de-duplication) - this all meaning slower
response times than what the middleware could have.
FWIW, I actually looked into doing this and now I understand what you
mean...I was trying to set up something that would work just like
`/latest` except it would get the latest result *per scenario*, not per
testcase...but indeed it turns out to be very tricky to do given how
the storage of the 'extradata' differs from the storage of the core
attributes for each result.
I kinda feel like it ought to be possible for someone with better
advanced-SQL-fu than me, though :)
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net