|author||Mark Brand <email@example.com>||2012-07-11 09:52:14 +0200|
|committer||Qt by Nokia <firstname.lastname@example.org>||2012-07-17 08:13:30 +0200|
QSqlTM: use generated flag more correctly in setRecord()/insertRecord()
The generated flag should affect the generation of SQL commands rather than how the fields of the source record are applied to the model before submitting. This correction allows setRecord() to be used to change TRUE generated flags to FALSE. Clarified documentation on this point and updated change log. Change-Id: I7ee124930822561ed8beee6c6259970b3e929c9b Reviewed-by: Michael Goddard <email@example.com>
Diffstat (limited to 'dist')
1 files changed, 3 insertions, 2 deletions
diff --git a/dist/changes-5.0.0 b/dist/changes-5.0.0
index 1dfbeaa35f..438885888f 100644
@@ -513,8 +513,9 @@ ignore the rest of the range.
removed and only if there are no other changed rows.
* setRecord() and insertRecord()
- -Only use fields where generated flag is set to true. This is
- is consistent with the meaning of the flag.
+ -The generated flags from the source record are preserved in the model
+ and determine which fields are included when changes are applied to
+ the database.
-Require all fields to map correctly. Previously fields that didn't
map were simply ignored.
-For OnManualSubmit, insertRecord() no longer leaves behind an empty