On 2008-10-08, Aaron Digulla wrote:
Scott Frankel schrieb:
This seems beyond the scope of
QSqlRelationalTableModel.
During my work on UPCScan, I've found that the QSqlRelationalTableModel
and the related table view are too buggy and too limited to be useful.
In the end, I've ripped all
Quoting Mark Summerfield [EMAIL PROTECTED]:
On 2008-10-08, Aaron Digulla wrote:
Scott Frankel schrieb:
This seems beyond the scope of
QSqlRelationalTableModel.
During my work on UPCScan, I've found that the QSqlRelationalTableModel
and the related table view are too buggy and too limited to
Scott Frankel schrieb:
This seems beyond the scope of
QSqlRelationalTableModel.
During my work on UPCScan, I've found that the QSqlRelationalTableModel
and the related table view are too buggy and too limited to be useful.
In the end, I've ripped all the code out again and wrote my own
Hello,
What's the proper way to perform sql SELECT statements to populate a
table model, when the statement is more complex than select(),
filters, and order clauses can handle?
According to the Qt documentation, QSqlTableModel.setQuery should
normally not be called on a
