QTableWidget and SQL (dynamic) not working
-
Hi,
You don't add any row to your QTableWidget or did you do before running that loop ?
Also, why not use a QTableView with QSqlQueryModel ?
-
Hi,
You don't add any row to your QTableWidget or did you do before running that loop ?
Also, why not use a QTableView with QSqlQueryModel ?
-
wrote on 9 Apr 2016, 14:20 last edited by
I can recommend reading these two articles to not only understand the model/view concept but also how Qt implements it:
As @SGaist pointed out there's an existing model that allows you to display SQL query results in a
QTableView. The model is calledQSqlQueryModel. You'd basically use aQTableViewinstead of aQTableWidgetand useQTableView::setModel()to set theQSqlQueryModelas the model for the table view. -
I can recommend reading these two articles to not only understand the model/view concept but also how Qt implements it:
As @SGaist pointed out there's an existing model that allows you to display SQL query results in a
QTableView. The model is calledQSqlQueryModel. You'd basically use aQTableViewinstead of aQTableWidgetand useQTableView::setModel()to set theQSqlQueryModelas the model for the table view.wrote on 9 Apr 2016, 21:16 last edited by@Joel-Bodenmann I tried to use QTableView but actually it would break a lot of my code so unless it's completely necessary I won't use it. I'm focusing on trying to solve my current issue.
-
What would break ?
In any case, I don't see you creating new rows. The incrementation of
idoesn't mean your QTableWidget will have an additional row unless you did it before your while loop. -
@Joel-Bodenmann I tried to use QTableView but actually it would break a lot of my code so unless it's completely necessary I won't use it. I'm focusing on trying to solve my current issue.
wrote on 9 Apr 2016, 22:14 last edited by Joel Bodenmann 4 Sept 2016, 22:16@cxam
QTableWidgetactually inherits fromQTableViewso it shouldn't break anything in terms of the GUI. In terms of the data handling: You just outsource that to the model. As there's an existing model that is designed specifically for handling SQL queries I can imagine that the only thing it would do is drastically simplify your life.
TheQTableWidgetreally is just aQTableViewwith an internal model. That model is a generic model. Using theQTableViewwould allow you to use the SQL query specificQSqlQueryModel.@SGaist
QTableWidget::setItem()actually creates the row internally. -
@cxam
QTableWidgetactually inherits fromQTableViewso it shouldn't break anything in terms of the GUI. In terms of the data handling: You just outsource that to the model. As there's an existing model that is designed specifically for handling SQL queries I can imagine that the only thing it would do is drastically simplify your life.
TheQTableWidgetreally is just aQTableViewwith an internal model. That model is a generic model. Using theQTableViewwould allow you to use the SQL query specificQSqlQueryModel.@SGaist
QTableWidget::setItem()actually creates the row internally.wrote on 9 Apr 2016, 22:29 last edited by@Joel-Bodenmann Hmm I see. I'll check it out then, thanks for your help.
-
@Joel-Bodenmann No it doesn't. First thing done, it checks whether the row, column combination returns a valid index if not then it returns immediately.
-
@Joel-Bodenmann No it doesn't. First thing done, it checks whether the row, column combination returns a valid index if not then it returns immediately.
wrote on 9 Apr 2016, 22:40 last edited by -
@Joel-Bodenmann No it doesn't. First thing done, it checks whether the row, column combination returns a valid index if not then it returns immediately.
wrote on 10 Apr 2016, 07:06 last edited by@SGaist Indeed, you're right When I set the properties for my table I set that the number of rows was "1" so I have to create an "int" variable and then say that the number of rows is that variable starting from 1 and then increment that number on the loop.
12/12