It seems from a quick test once you start to include the QSqlTableModel which QSqlRelationalTableModel extends from; there is a big delay iteration time. I would think I would want to avoid this class if I don't need it and can get by on QSqlQueryModel. Overloading QSqlQueryModel so it can write to the database also would be the only feature I think I need that the relational model has; which I have learned to work around.

Still learning these class types and I know there are hidden potentials to them also. Thought I should ask.