On 12/08/2012 01:11 PM, Kohsuke Kawaguchi wrote:
Map is by definition single index, so I'm not sure it works for many typical
use cases. Say test reports—we need to be able to
query all failing ones for a given build as well as all the past executions of
a specific test case.
What is stopping you from creating several maps, corresponding to the indices
you care about for this plugin?
I see no advantage in nontrivial SQL queries for Jenkins, since the reason to have SQL be able to perform queries beyond looking up the value for an indexed key is to
offload processing from the client to the DB server to avoid excessive network traffic. For an embedded DB this is a nonissue: you can write whatever
predicates/filtering/sorting/grouping/etc. you want in Java code (and more easily and flexibly).
Supporting user-defined queries seems vastly less important than having efficient and compact data storage. And as far as familiarity of API is concerned, MapDB is much
simpler than JDBC; anyway the audience for this API is a few people writing plugins such as JaCoCo.
