Bug 9117 - Allow "project builds" and "all builds" to be sorted by time and recipe name
Summary: Allow "project builds" and "all builds" to be sorted by time and recipe name
Status: NEW
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Low normal
Target Milestone: Future
Assignee: Toaster default assignee
QA Contact: yeoh ee peng
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-02-15 16:44 UTC by Elliot Smith
Modified: 2023-12-14 04:17 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elliot Smith 2016-02-15 16:44:10 UTC
When the "builds" tables were converted to ToasterTable, the recipe name sort was removed as it depended on a derived property (recipe__name), and ToasterTable doesn't support sorting by derived properties.

The time sort was already disabled on the "builds" tables, but this also needs to be put back in. Again, this is a derived field.

The same approach taken for number of errors and number of warnings (for the Builds table) might be possible, where derived fields are added to the objects in the queryset via annotations. A queryset can be sorted by a field which is an annotation. However, most examples of annotation use counts, rather than calculations on existing fields on a model.