Database and QSqlRelationalTableModel problem

[harryf]

Are you calling select() on your model? setTableName() only populates the headers, but does not execute a query to fetch the data.

Also:

m_pTableRecord=&pDatabase->m_Database.record(sTableName); // fetches column names

this line is scary - you are taking the address of a temporary object. m_pTableRecord becomes a dangling pointer!

[MarkoSan]

Are you calling select() on your model? setTableName() only populates the headers, but does not execute a query to fetch the data.

Also:

m_pTableRecord=&pDatabase->m_Database.record(sTableName); // fetches column names

this line is scary - you are taking the address of a temporary object. m_pTableRecord becomes a dangling pointer!

I am dealing with this line right now, marcel helped me a lot with it. But for now, I've chcked, column names are fetched correctly. I will check now for select() method execution. Thanks a lot for now.

[MarkoSan]

I finally solved the problem, I had m_pModel on two different places (in CDatabaseFoundation and in CBrowserWindow). I've deleted the one in CBrowserWindow and works fine. For future references, what do you think, where should be m_pModel (QSqlRelationTableModel) declared in class that handles database connection or in class that handles record browsing?

[harryf]

A database model encapsulates a result set sent from the database. I would always keep it as local as possible (in your case, in the record browsing class) to prevent concurrency errors (e.g. when refactoring, two views might end up accessing the same model leading to strange race conditions).