Mark Brand 10ff9de91b QSqlTableModel: don't cache unchanged value in setData() ... This is good for performance in terms of avoiding unnecessary database activity and keeping the cache smaller. Detail: This change was not included in the big refactoring of QSqlTM. The idea was that the model shouldn't second guess the intention of the application and maybe the application wants to cause a submit. It was a marginal consideration. Now I think it's clear that our interest in not unnecessarily expanding the cache outweighs that. In addition, applications can now call selectRow() if they worry that the database values for the row have changed and want to set a value back again. Test added. Change-Id: I63814dcb63a96c6ba1c8cc227807725a954a0b68 Reviewed-by: Marc Mutz <marc.mutz@kdab.com> Reviewed-by: David Faure <david.faure@kdab.com>		2012-10-05 03:16:19 +02:00
..
kernel	Change copyrights from Nokia to Digia	2012-09-22 19:20:11 +02:00
models	QSqlTableModel: don't cache unchanged value in setData()	2012-10-05 03:16:19 +02:00
sql.pro	Moved sql autotests into new directory structure	2011-09-06 09:32:15 +02:00