Andy Shaw ae42461f44 MySQL: Handle TIME types as a string to allow the full range of data ... As the full range of TIME is '-838:59:59' to '838:59:59' then we cannot use QTime as the object to store this data in. Therefore a QString is used instead for passing the data to and from. This does not impact existing code using QTime already as it will still convert it from the QString to a QTime to give the same result as before. [ChangeLog][QtSql][MySQL] The TIME data type is now treated like a string-based type in order to respect the full range of the TIME data type. Task-number: QTBUG-57028 Change-Id: Ieb7105bff3043b845f76bc873d088e6bac1e4f10 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>		2018-06-06 11:14:03 +00:00
..
qsql	tst_qsql.cpp: Remove deprecated module include	2016-11-25 09:55:21 +00:00
qsqldatabase	QSqlDatabase: Skip confusing thread warning on invalid QSqlDatabase	2018-04-06 07:18:03 +00:00
qsqldriver	OCI: Match the constraints on the index_name column	2017-11-15 06:40:45 +00:00
qsqlerror	Add move special member functions to QSqlError	2017-04-28 12:50:34 +00:00
qsqlfield	QSqlField: Add a means to see what the tablename is for a given field	2017-07-12 09:01:50 +00:00
qsqlquery	MySQL: Handle TIME types as a string to allow the full range of data	2018-06-06 11:14:03 +00:00
qsqlrecord	QSqlField: Add a means to see what the tablename is for a given field	2017-07-12 09:01:50 +00:00
qsqlresult	Updated license headers	2016-01-21 18:55:18 +00:00
qsqlthread	Fix invalid placeholder name in tst_qsqlthread.cpp	2017-08-23 12:48:32 +00:00
kernel.pro	SQL: Change in QSqlResultPrivate::positionalToNamedBinding()	2012-12-10 21:23:35 +01:00