Code review comment for lp:~cjwatson/launchpad/git-getRequestedReviews

Hm. Possibly, and fixing that is difficult with the current structure (CodeReviewComment.vote isn't in the UNIONed result set). I'm thinking that the best way to tackle this might be to do something like what we did with Snap, and move the queries for merge proposals on collections to the BranchMergeProposal model so that we can use a simple OR here rather than a UNION. We would have to think carefully about how to design the bits that remain on *Collection - there'd have to be some reasonable way to extract symmetric vs. asymmetric expressions - but we'd probably still end up with a net reduction of code as well as being able to support this case. Does that sound reasonable?