|
Why are you creating yet another class instead of properly structuring your application? Take a gander at http://www.logikalsolutions.com/wordpress/information-technology/qt-and-usb-pt-4/ for some ideas. You probably also want to find a copy of this book http://www.theminimumyouneedtoknow.com/qt_book.html Most importantly you need to read the fine manual. http://doc.qt.io/qt-5/qsqldatabase.html#dtor.QSqlDatabase QSqlDatabase::~QSqlDatabase()Destroys the object and frees any allocated resources. Note: When the last connection is destroyed, the destructor implicitly calls close() to release the database connection. See also close(). If your database is open for the life of the application then the
application has a failed architecture. Database connections aren't
supposed to have actual life spans. On 08/21/2018 03:08 PM, Israel Brewster
wrote:
Ideally, what I'd have is a system where you set up the connection, and then it automatically opens/closes the connection when needed (i.e. when doing a SELECT, INSERT, UPDATE, etc). With my app, this would generally only be for a) periodic updates or b) in direct response to user input, so most of the time the connection could remain closed. To the best of my knowledge (correct me if I am wrong), this is not possible with the existing QSqlDatabase/ QSQLITE database driver classes. -- Roland Hughes, President Logikal Solutions (630) 205-1593 http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.johnsmith-book.com http://www.logikalblog.com http://www.interestingauthors.com/blog http://lesedi.us |
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
