-
Bug
-
Resolution: Done
-
P1: Critical
-
5.15.2
-
None
-
Linux x86_64
-
Linux/X11
-
549ee216fd5bf2b3810e940bcbd4bbd8c64ac73f (qt/qtbase/dev) 94d22e0bcc893448d53b718f4a2732bd13fc21e4 (qt/qtbase/6.2) b3e0cdedc681c27e9b2b2dcdd4f1e1420adf5a73 (qt/qtbase/5.12) 1c6066148c (qt/tqtc-qtbase/5.15) 1c6066148c (qt/tqtc-qtbase/tqtc/vxworks-5.15.10)
MariaDB 10.6 introduced cached metadata for prepared queries:
https://github.com/MariaDB/server/commit/295f3e4cfb4a8f132f36d53475efc92f2487aa97
This has been identified to cause breakage in applications using Qt's mysql driver:
digikam:
https://bugs.archlinux.org/task/71582
https://bugs.kde.org/show_bug.cgi?id=440296
mythtv:
https://bugs.archlinux.org/task/71753
https://github.com/MythTV/mythtv/issues/373
Note that, due to QTBUG-95071, this is not noticeable in unpatched Qt, because the two bugs "cancel each other out": QTBUG-95071 causes MariaDB 10.6 to be identified as an old version not supporting prepared queries, so these issues don't happen (but that's obviously just an accident)
- relates to
-
-
- Closed
-
| For Gerrit Dashboard: QTBUG-95639 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 364843,4 | MySQL: treat the MYSQL_FIELD as read-only | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 365471,2 | MySQL: treat the MYSQL_FIELD as read-only | 6.2 | qt/qtbase | Status: MERGED | +2 | 0 |
| 365472,3 | MySQL: treat the MYSQL_FIELD as read-only | 5.12 | qt/qtbase | Status: MERGED | -1 | 0 |
| 365473,3 | MySQL: treat the MYSQL_FIELD as read-only | tqtc/lts-5.15 | qt/tqtc-qtbase | Status: MERGED | +2 | 0 |