path: root/dist
diff options
authorMark Brand <>2012-02-21 09:22:26 +0100
committerQt by Nokia <>2012-03-07 00:01:32 +0100
commit888fed8065f708baeb6efa5f280c2f1aec3dee78 (patch)
tree6d90aecef3b489d9cf4ad1d2880b173cbe749c44 /dist
parent291e2c7d5416af4d16dc0a6e60df7980ba745a3d (diff)
QSqlTableModel: use selectRow() for field and row edit strategies
Calling select refreshes the query data but disrupts view navigation. For OnFieldChange and OnRecordChange it makes sense to only select the row in question. This does not disturb view navigation. Assume disruption of view navigation is not a problem for OnManualSubmit because the user or application decides when submitAll is called. Task-number: QTBUG-2875 Change-Id: I1e5f68668fb9102f6296d67d543e80daa403f1c4 Reviewed-by: Yunqiao Yin <>
Diffstat (limited to 'dist')
1 files changed, 8 insertions, 0 deletions
diff --git a/dist/changes-5.0.0 b/dist/changes-5.0.0
index dd0a0693ed..33a8869397 100644
--- a/dist/changes-5.0.0
+++ b/dist/changes-5.0.0
@@ -406,6 +406,14 @@ ignore the rest of the range.
QSqlTableModel::indexInQuery() as example of how to implement in a
+* QSqlTableModel edit strategies OnFieldChange/OnRowChange QTBUG-2875
+Previously, after changes were submitted in these edit strategies, select()
+was called which removed and inserted all rows. This ruined navigation
+in QTableView. Now, with these edit strategies, there is no implicit select()
+done after committing. This includes deleted rows which remain in
+the model as blank rows until the application calls select(). Instead,
+selectRow() is called to refresh only the affected row.
* Database Drivers *