Bug 1102228 improve data cycling

See commit message
isn't there some kind of "cascading delete" that we could use with the foreign keys?  seems like that would make this whole process simpler.  You wouldn't have to find the revisions and jobs.  Just deleting the resultset would kill all the children.  Or is that not performant somehow?