QSqlQuery::exec() freezes over OpenVPN

petar

Ok, and then what. Suppose the query in another thread succeeds. How can I use that query in main thread and attach it to a QSqlQueryModel model and display data in QTableView?

If the query freezes in another thread, I suppose I can handle that with some timeout. Is there a way to kill the thread that left frozen?

A.A.SEZEN

I think you should focus on OpenVPN for the solution.
There is no query timeout in this sense mentioned in the SQLite documents.
However, the problem of freezing with OpenVPN is mentioned in internet searches.

JonB

@petar

Ok, and then what. Suppose the query in another thread succeeds. How can I use that query in main thread and attach it to a QSqlQueryModel model and display data in QTableView?

I presume that you would put your QSqlQueryModel in its own background thread while keeping the QTableView in the main, GUI thread. Can someone confirm that the model signals to the view slots would work fine across threads (hmm....), or does one have to do something else?

petar

@A-A-SEZEN
Ok, it is PostgreSQL but maybe it's irrelevant. What i wanted to say is that it is a (serious) bug in Qt. QSqlQuery::exec() shouldn't freeze under any circumstances. It's not a problem to me if the query returns false because of too many records or whatever. But it freezes my whole app. QSqlQuery::exec() has to be somehow implemented that it can't freeze.

petar

@JonB
Maybe you are right. I don't know if it is doable.

But the whole point is that if QSqlQuery::exec() would work ok, then there would be no need for another thread, because query (for 25-50,000 records) takes only few seconds over OpenVPN, and that is acceptable, and if query returns false, i can retrieve fewer records (LIMIT, or segment it,...) in another try or do whatever I want, but don't freeze the whole app for God's sake.

For example, what if the network (over OpenVPN) is gone right before I start QSqlQuery::exec(), should it really freeze?

Or just return false.

JonB

@petar
The Qt SQL stuff uses drivers to do the low-level stuff. It may not be a "fault" in QSqlQuery::exec(), it may be the underlying protocol talking to SQL over OpenVPN which is what "freezes", and there is nothing the Qt level can do about that.

petar

@JonB
Aren't those drivers a part of Qt (eg. QPSQL for Postgres), it's not external driver.

JonB

@petar
Yes, but ultimately they must leverage some lower-level protocol code (e.g. ODBC, or whatever for MySQL or Postgres), and that is where it may be "freezing" over OpenVPN? I was just saying it may not be QSqlQuery::exec() code itself, which may be built atop other levels, which freezes, and it may not be able to do anything about it, which you are asking it to do.

A.A.SEZEN

@petar said in QSqlQuery::exec() freezes over OpenVPN:

Ok, and then what. Suppose the query in another thread succeeds. How can I use that query in main thread and attach it to a QSqlQueryModel model and display data in QTableView?
If the query freezes in another thread, I suppose I can handle that with some timeout. Is there a way to kill the thread that left frozen?

Yes.

void MainWindow::threadStart()
{
    threadQuery * tQuery = new threadQuery;
    connect(tQuery, &threadQuery::record, this, &MainWindow::record);
    tQuery->start();
}

void MainWindow::record(QSqlQueryModel *model)
{
    ui->tableView->setModel(model);
}

void threadQuery::run()
{
    QSqlQuery q(conn);
    if(q.exec("SELECT * FROM table")) {
        model->setQuery(q);
        emit this->record(model);
    }

}

petar

@A-A-SEZEN
Ok, thanks, but what about this limit from the documentation?

It says: "A connection can only be used from within the thread that created it. Moving connections between threads or creating queries from a different thread is not supported."

How can I further work with this query/model in my main thread?

What happens when your code in thread:

if(q.exec("SELECT * FROM table")) {

(precisely exec() function) freezes?

A.A.SEZEN

@petar
Your application will not freeze due to Thread.
You know the integrity of your code.

JonB

@A-A-SEZEN

    QSqlQuery q(conn);
    if(q.exec("SELECT * FROM table")) {
        model->setQuery(q);

I don't know, but have you verified whether this does not execute the query twice?

petar

@JonB
No, only once.

petar

@A-A-SEZEN
Can I use thread for queries working with QSqlQuery and QSqlQueryModel? I am not sure. What about sharing connections (that is not allowed) between threads, and sharing queries?

jsulm

@petar said in QSqlQuery::exec() freezes over OpenVPN:

Aren't those drivers a part of Qt (eg. QPSQL for Postgres), it's not external driver.

Those use client libraries provided by the SQL database system like libmysqlclient for MySQL. To see whether this is an issue in Qt or database system you can try to execute exactly the same query over VPN with the client application of your database system.

petar

@jsulm
Good point. I checked the same query over OpenVPN with LIMIT 25,000 - 200,000 records in Qt and in plain psql. In Qt QSqlQuery::exec() almost always freezes, while psql never.

petar

I tested it and it turns out it freezes even in non GUI applications, so it doesn't have to do anything with the GUI thing.

I just started QSqlQuery::exec() in non GUI app and it freezes forever over OpenVPN, while the same code works ok over LAN or on localhost. On LAN sometimes QSqlQuery::exec() returns false which is ok, but never freezes forever.

A.A.SEZEN

@petar said in QSqlQuery::exec() freezes over OpenVPN:

Can I use thread for queries working with QSqlQuery and QSqlQueryModel? I am not sure. What about sharing connections (that is not allowed) between threads, and sharing queries?

The codes above are thread codes I've tried for you.
I've already shared critical parts. The rest are standard thread class and database connections. It is up to you how much you can use within the integrity of your code.
SQLite does not allow concurrent operations to the same table. Other than that, you will have no problems. You can create a new SQLite connection in a thread, or you can include your connection class in a thread class. I have used both cases. I like to manage it myself instead of the model. I am using QTableWidget instead of QTableView. So I can't comment much on your situation.
Regards.

jsulm

@petar You can check Qt bug tracker and file a bug if there is nothing yet for this issue

petar

@jsulm
I've already done this but got the answer from Christian Ehrlicher that this is probably a bug inside the libpq Postgres lib and that there is nothing they can do about it (concerning Qt).