QPSQL: Unable to find table set in a QSqlTableModel

[andreabiscuola]

Hi norobro.

currentConnection is properly initialized and database test is going ok. I'm working with PostgreSQL 9.0.2.
I think that this is a problem relative to the query syntax posted from QPSQL to the database engine. Have you read nothing abount this? Do you know a method to show the last query executed on the database?

Thanks

[andreabiscuola]

Updates:

I tried to debug my database stack with a QDebug object and the result are:

- There is no errors for database connection, it result correctly up and running.
- There is no errors for the last database transaction executed. Operation required to the QSqlDatabase connection is ok.
- If i try to execute a QSqlQuery statement with my required query (wroted by hand), it fetch data from PostgreSQL correctly and i can bind all the values in the record.

My Opnion:
I think that this is a problem only of the QSqlTableModel stack and for query inserted with model functions. Now i try to give to the model a Query written by hand.

[norobro]

Hi Andrea,

Take a look this bug report.

My test app worked fine on postgres 8.4 but after upgrading 9.0.1 I got the following warning on the command line: "This version of PostgreSQL is not supported and may not work." Plus lastError() reported "unable to find table foo".

After applying the patch in the bug report and recompiling the psql driver it works.

BTW I'm using Qt 4.7.0

HTH
Norm

[ChrisW67]

I think that this is a problem relative to the query syntax posted from QPSQL to the database engine. Have you read nothing abount this? Do you know a method to show the last query executed on the database?

QSqlTableModel::selectStatement() should give you the query the model will try to execute.

[andreabiscuola]

Hi norobro!

The bug report you indicated respond completely to my problem! I want to try the patch suggested but i have a doubt: Why the problem appear only using the QSqlTableModel and not with the QSqlQuery?

[norobro]

Here is a thread on Qt-interest about this.

Why the problem appear only using the QSqlTableModel and not with the QSqlQuery?

I guess you could dig into the source code to figure out why