I think that is the right approach for now. For simple queries ("SELECT * from lists.People"), the primary key should be pulled through and used as the record selector value, but we don't do anything for queries with joins.

Perhaps we could add a property to QueryWebPart to set the underlying DataRegion's 'recordSelectorValueColumns'.