Milian Wolff 3370ab9119 Never return char variants when reading prepared MySQL statements ... This has undesired effects when converting a QSqlRecord to JSON. A char(0) e.g. has special semantics that are undesired when reading a Tinyint column. I don't think that returning bool for the special case of a Tinyint(1) is required. This also did not happen before, and is also not happening when not using a prepared statement. Instead, a plain int/uint QVariant is returned. This patch extends tst_QSqlQuery::integralTypesMysql to also cover reading and writing booleans from/to a MySQL table column of type Tinyint(1). Additionally, the reading is now also done with a prepared statement and we also check the raw variant value. The broken behavior fixed by this patch was introduced by me in commit 194403a348. Change-Id: I028a3abd83fdd2b42d98d478950d205e5b6bbeb5 Task-number: QTBUG-53397 Reviewed-by: Andy Shaw <andy.shaw@qt.io>		2016-09-12 12:47:08 +00:00
..
kernel	Never return char variants when reading prepared MySQL statements	2016-09-12 12:47:08 +00:00
models	QSqlDriver: use table prefix in WHERE clauses	2016-02-17 23:13:58 +00:00
sql.pro	Moved sql autotests into new directory structure	2011-09-06 09:32:15 +02:00