From 108748404beb607538ea965a21fa932d275eecdd Mon Sep 17 00:00:00 2001 From: Mark Brand Date: Tue, 13 Mar 2012 01:28:35 +0100 Subject: QSqlTableModel::setData(): no longer autosubmit for OnRowChange The model can never do a good job of knowing when user moves to a new row in the view. Faking it by detecting when another row is changed was not a good solution because it cannot detect when the last edited row is left. Either the view should automatically submit when the user leaves a row or the application should provide a way to submit. This change made it possible to reuse the logic of flags() in setData(). Change-Id: I2550e5b113bceba1a852fc21203babeca07c5748 Reviewed-by: Honglei Zhang --- dist/changes-5.0.0 | 2 ++ 1 file changed, 2 insertions(+) (limited to 'dist/changes-5.0.0') diff --git a/dist/changes-5.0.0 b/dist/changes-5.0.0 index e10f0df195..ebe8ad5331 100644 --- a/dist/changes-5.0.0 +++ b/dist/changes-5.0.0 @@ -446,6 +446,8 @@ Instead, pending (failed) changes cause new changes inappropriate to the edit strategy to be refused. The application should resolve or revert pending changes. insertRows() and insertRecord() also respect the edit strategy. +* QSqlTableModel::setData() and setRecord() in OnRowChange no longer have the +side effect of submitting the cached row when invoked on a different row. **************************************************************************** * Database Drivers * **************************************************************************** -- cgit v1.2.3