Thank you both for the helpful info! Unfortunately I don't think the KDescendantsProxyModel will quite work for me since it turns the result into a list, when really I need a table (not clear from my initial post, apologies). What I left out in my simplified example is that I still need all the extra data associated with each child (e.g. color, price, etc.). It seems that perhaps the best solution is to create a custom proxy model and put the resulting children into a table view rather than a tree view (at least, I'm assuming it should be a tableview since there won't be nodes). I spent a few hours yesterday trying to wrap my head around proxy models, and I think it will be the best solution. I believe that the relationship between the parents and children is simple enough that I shouldn't need two separate models.