https://bugs.kde.org/show_bug.cgi?id=391783
--- Comment #2 from Allan Sandfeld <k...@carewolf.com> --- Yes upon further investigation this mainly seems to be trigger by the use of default constructed QSqlQuery as a non-initialized null value, but that is not how Qt treats them, and they will try to connect to the default database and prepare to execute commands there. -- You are receiving this mail because: You are the assignee for the bug.
