Add documentation about not having QSqlDatabase objects kept around

Task-number: QTBUG-35977
Change-Id: I8601b3f7379a5fe94898a2f5ff63558a896a4de2
Reviewed-by: Venugopal Shivashankar <Venugopal.Shivashankar@qt.io>
bb10
Andy Shaw 2017-09-07 21:45:02 +02:00
parent 202d3ba3e6
commit 452ad2bb13
1 changed files with 8 additions and 0 deletions

View File

@ -365,6 +365,14 @@ void QSqlDatabasePrivate::disable()
cloneDatabase() to create an independent database connection based
on an existing one.
\warning It is highly recommended that you do not keep a copy of the
QSqlDatabase around as a member of a class, as this will prevent the
instance from being correctly cleaned up on shutdown. If you need to
access an existing QSqlDatabase, it should be accessed with database().
If you chose to have a QSqlDatabase member variable, this needs to be
deleted before the QCoreApplication instance is deleted, otherwise it
may lead to undefined behavior.
If you create multiple database connections, specify a unique
connection name for each one, when you call addDatabase(). Use
database() with a connection name to get that connection. Use