I wouldn't use QSqlQueryModel in such a case. As you said it is a table model.
Since it is just a convenience wrapper to present the result of an SQL query in a table, it is just doing things that are not needed here.
You can, of course, use a proxy for that, but why go through the complexity of a proxy when you can present the data in the way you want to in the first place.
You would still have to synchronize the two selection models since the two views are working with different models.
Cheers,
_
Bookmarks