QSqlTableModel, QTableView and complex queries

**Walter** · 6th August 2009, 10:38

Some infos as requested:

I've finalized my own QSqlQuery subclass but in a way that is very specific to my needs. What I have:

3 Classes for a database repository that knows what the tables, fields and primary keys should be. Why? First, the database may be in a state that is corrupt. Second, the repository knows much more than the few infos that the database is able to give me.

My own query class derived from QSqlQuery. The class is able to generate SQL statements fro select, insert, update, delete. The select part is able to generate correct joins. Currently I work on support for outer joins on all supported databases.

My own delegates can access the repository and in a table view draw the columns in an application specific way.

**toroman** · 9th October 2009, 01:03

Walter,
You couldn't be more right about this...
The implementation of QSql***model classes are sufficient only for basic use of databases from my expirience.

I wonder if people from Nokia plan to do something about it in future releases. It is not that hard to figure out what is needed if you have ANY experience (apart from very basic examples provided) in database programming. I'm also new to Qt (expirienced developer but not in Qt) and I was very disapointed by the implementaton.

Otherwise, we will have to follow your approach - make our own classes...