QsqlTableModel not fetching all rows after update

[KillGabio]

Thank you for replying. Line 51 modified :P

I tried calling the reset but nothing changes. Rows showed change to 256 after the edit.

There is no selection, the user only changes the value of one cell so i think i dont have to iterate, right? So i call setData() from the index of interest but still the same, rows trim to 256.

void WidgetModificacion::actualizar_fecha (int row, QSqlRecord & record){
    if (tipo_tabla == 0){
        QSqlQuery query = QSqlQuery (db);
        query.prepare("UPDATE TABLE_PRODUCTOS SET fecha_modificacion = SYSDATE WHERE id_codigo_barra = :value");
        query.bindValue (":value", this->ui->tableView->model ()->data (this->ui->tableView->model ()->index (row, 0)).toString ());
        query.exec ();
    }
    //ui->tableView->reset();
    model->setData(model->index(row,5), QDateTime::currentDateTime().toString(),Qt::DisplayRole);
    while (model->canFetchMore())model->fetchMore();
}

void WidgetModificacion::actualizar_fecha (int row, QSqlRecord & record){
    if (tipo_tabla == 0){
        QSqlQuery query = QSqlQuery (db);
        query.prepare("UPDATE TABLE_PRODUCTOS SET fecha_modificacion = SYSDATE WHERE id_codigo_barra = :value");
        query.bindValue (":value", this->ui->tableView->model ()->data (this->ui->tableView->model ()->index (row, 0)).toString ());
        query.exec ();
    }
    //ui->tableView->reset();
    model->setData(model->index(row,5), QDateTime::currentDateTime().toString(),Qt::DisplayRole);
    while (model->canFetchMore())model->fetchMore();
}

To copy to clipboard, switch view to plain text mode 

The value is always updated after edit and i can see that value modified but rows set to 256 anyways.

[ChrisW67]

You reset the QSqlTableModel and it re-executes the underlying query and, as always, fetches rows lazily. If you want to fetch all the rows again then use canFetchMore() and fetchMore().

If you are only updating a single cell then look up its QModelIndex and call setData() and the view will look after itself. Exactly when that update is written to the underlying database and the effect on selections/current cell is a function of the model's edit strategy.