Skip to content

models: don't use mesa sha as ID/primary key for Build table

clayton craft requested to merge perf_next into master

This prevents having builds from different jobs for the same mesa sha. Instead, the existing index of sha + job should be enough to query (and indeed most/all queries of the Build table are with that)

Merge request reports