Mark Brand b979956ec4 QSqlTableModel: handle changes between submit and select ... Once an insert has been submitted, the cached record behaves like an update. For row bookkeeping, we still have to remember that it was originally inserted and is not in the query rows. Between submitting a delete and selecting, we remove the values from the deleted record. This causes a blank row to be displayed. Read-only flag is set for cells in deleted row. Reverting between submit and select means going back to the last submitted values. When removing rows, it's better to process from highest row numbers to lowest. This avoids complications with higher rows shifting down when lower rows are removed. Change-Id: I8752fa11f7a1b88f2a71b9e03a020ac37e62487f Reviewed-by: Honglei Zhang <honglei.zhang@nokia.com>		2012-03-07 00:01:07 +01:00
..
.gitignore	Moved sql autotests into new directory structure	2011-09-06 09:32:15 +02:00
qsqltablemodel.pro	all remaining tests: eliminated usage of qttest_p4.prf	2011-10-25 08:42:23 +02:00
tst_qsqltablemodel.cpp	QSqlTableModel: handle changes between submit and select	2012-03-07 00:01:07 +01:00