[Solved] Qt: strange behaviour after last qt5-base update

rogorido · 2017-11-20 18:20:20

seth wrote:

"model.QSqlQueryModel::setQuery(.)"

THis works. But what does it really means? At the moment I'm totally confused with all this story...

rogorido · 2017-11-20 18:23:48

Trilby wrote:

When you say you get the "same error" with my suggested revision, does that mean the function returned false indicating an error - or just that the same error text was found in the error class.

Thanks again for your help. If I understand you correctly: the if statement is evaluated to yes and I get the error (tablen not found).

Also what about the documentation note I quoted? It sounds like rowCount is supposed to return zero if all is well under the conditions in which you used it. As that was initially the only indication of a problem, I fail to see what issue is being chased down here. It may seem silly for rowCount to return zero, but that is the documented behavior (unless I'm misreading it).

I have to admit, this is very illogical for me... Anycase: til saturday instantiating QSqlTableModels got the data from the tables and my QTableViews got populated...

seth · 2017-11-20 20:25:09

It means that the database model basically "works" - the explicit call to the base class function sidesteps the protection in the leaf class.

What's

qDebug() << model.tables();

(regardless of setTable/setQuery)?

rogorido · 2017-11-20 21:33:50

seth wrote:

It means that the database model basically "works" - the explicit call to the base class function sidesteps the protection in the leaf class.
What's
qDebug() << model.tables();
(regardless of setTable/setQuery)?

I suppose you mean:

qDebug() << db.tables();

I get a list of my tables in the db... Really confusing...

seth · 2017-11-20 21:38:36

Yes, sorry. What does it look like, and what happens if you use eg. "setTable(db.tables().at(0))" instead of the hardcoded string?

rogorido · 2017-11-21 08:19:55

seth wrote:

Yes, sorry. What does it look like, and what happens if you use eg. "setTable(db.tables().at(0))" instead of the hardcoded string?

Same error: unable to find table places and 0 rows returned...

rogorido · 2017-11-25 14:44:37

As I imagine, it was a problem with the qt5-base update. The update to qt5-base 5.9.3(-1) of today (25th nov) solves the problem.

Arch Linux

#26 2017-11-20 18:20:20

Re: [Solved] Qt: strange behaviour after last qt5-base update

#27 2017-11-20 18:23:48

Re: [Solved] Qt: strange behaviour after last qt5-base update

#28 2017-11-20 20:25:09

Re: [Solved] Qt: strange behaviour after last qt5-base update

#29 2017-11-20 21:33:50

Re: [Solved] Qt: strange behaviour after last qt5-base update

#30 2017-11-20 21:38:36

Re: [Solved] Qt: strange behaviour after last qt5-base update

#31 2017-11-21 08:19:55

Re: [Solved] Qt: strange behaviour after last qt5-base update

#32 2017-11-25 14:44:37

Re: [Solved] Qt: strange behaviour after last qt5-base update

Board footer