Red Hat Bugzilla – Bug 860888
RecipeTask ordering is not persisted
Last modified: 2016-05-26 09:15:01 EDT
Ordering of tasks within a recipe is significant (recipes have a sequence of tasks, not a set) but Beaker does not persist the ordering to the database. It relies on the tasks being assigned increasing ids when inserted, and on the fact that the database happens to return the rows in id order when queried.
At the very least Beaker should use ORDER BY id whenever it fetches RecipeTasks.
Having an explicit ordinal for each task in a recipe would come in handy when trying to write SQL queries which join recipe-tasks against recipe-tasks at the same position in different recipes. (I was trying to write a query like that last night for bug 960434.)