Does 'QSqlQueryModel' have a bug?

[schnitzel]

according to QSqlTableModel::setQuery documentation:

void QSqlTableModel::setQuery ( const QSqlQuery & query ) [protected]
This function simply calls QSqlQueryModel::setQuery(query). You should normally not call it on a QSqlTableModel. Instead, use setTable(), setSort(), setFilter(), etc., to set up the query.

See also selectStatement().

try setFilter() on the QSqlTableModel, just like the documentation suggests or use the QSqlQueryModel.

[nuntawat]

according to QSqlTableModel::setQuery documentation:




try setFilter() on the QSqlTableModel, just like the documentation suggests or use the QSqlQueryModel.

Sorry, but acrtually I would like to query using either QSqlQueryModel or QSqlTableModel (depending on a situation) from more than one table. So I need to set up the query myself. Does anyone have the solution?

[waynew]

Did you #include <QSqlQueryModel> ? That would give you the same error if you did not.

[nuntawat]

Did you #include <QSqlQueryModel> ? That would give you the same error if you did not.

I think the only way to use setQuery() function is passing string directly; noth tr() and QString can't be passed into that function.

But now I have a problem because I would like to use the QSqlQueryModel to fetch the data with specific condition (WHERE clause) and then display, but I can't add it to the query string which must be passed directly as I told before, and furthermore there is no function like setFilter() as QSqlTableModel has.

I'm very appreciated if you or any one post a solution. Thanks!!

[waynew]

That is not true. You can do this (it works in my code):

QSqlQuery query;
query.prepare("SELECT * from table_name where column = ?");
query.addBindValue("value");
query.exec();
model->setQuery(query);

QSqlQuery query;
query.prepare("SELECT * from table_name where column = ?");
query.addBindValue("value");
query.exec();
model->setQuery(query);

To copy to clipboard, switch view to plain text mode 

[nuntawat]

That is not true. You can do this (it works in my code):

QSqlQuery query;
query.prepare("SELECT * from table_name where column = ?");
query.addBindValue("value");
query.exec();
model->setQuery(query);

QSqlQuery query;
query.prepare("SELECT * from table_name where column = ?");
query.addBindValue("value");
query.exec();
model->setQuery(query);

To copy to clipboard, switch view to plain text mode 

Thanks!!! I just knew that setQuery() didn't execute the query!!

[wysota]

I think the only way to use setQuery() function is passing string directly; noth tr() and QString can't be passed into that function.

Hmm? That's not true.

But now I have a problem because I would like to use the QSqlQueryModel to fetch the data with specific condition (WHERE clause) and then display, but I can't add it to the query string which must be passed directly as I told before, and furthermore there is no function like setFilter() as QSqlTableModel has.

The table model is for representing a single table, you can't query for data from more than one table using that. You can't use setQuery() on QSqlTableModel as this wouldn't make sense - what differs QSqlTableModel and QSqlQueryModel is the query itself. If you overrode that, the table model could not execute its query anymore, that's why it is protected in QSqlTableModel. setFilter() only sets the WHERE clause on the model's query, it will influence rows, not columns. Functionally the two models are alike with the only exception that the table model is able to insert new rows into the table.

[ajg85]

as wysota pointed out what you are attempting conflicts with documentation:

void QSqlTableModel::setQuery ( const QSqlQuery & query ) [protected]
This function simply calls QSqlQueryModel::setQuery(query). You should normally not call it on a QSqlTableModel. Instead, use setTable(), setSort(), setFilter(), etc., to set up the query.

See also selectStatement().

Not only does setQuery not accept a string it is protected which means unless you make your own class which inherits from QSqlTableModel and sets the query internally this will cause a compile error. Regardless the query needs to be a single table select statement I believe.

Calling setTable will fetch the column information and setup your SELECT and FROM clauses.
Calling setFilter will setup your WHERE clause with the predicates you specify.
Calling setSort will setup your ORDER BY clause with column and ascending or descending keyword.

The minimum required before calling select() to populate the data is setTable which if used alone will basically do SELECT * FROM tablename except it will explicitly select columns so the order is guaranteed.