diff options
| author | Mark Brand <mabrand@mabrand.nl> | 2012-03-13 01:28:35 +0100 |
|---|---|---|
| committer | Qt by Nokia <qt-info@nokia.com> | 2012-03-15 15:35:32 +0100 |
| commit | 108748404beb607538ea965a21fa932d275eecdd (patch) | |
| tree | e2d8f5b11ea3b2897d0dd2f61fcfdcbff10d4bdc /dist | |
| parent | 3d7cec6577fa32fb6036b346db57c53e38ea2ffd (diff) | |
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 <honglei.zhang@nokia.com>
Diffstat (limited to 'dist')
| -rw-r--r-- | dist/changes-5.0.0 | 2 |
1 files changed, 2 insertions, 0 deletions
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 * **************************************************************************** |