Closed (fixed)
Project:
Drupal core
Version:
9.5.x-dev
Component:
mysql db driver
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
15 Jul 2022 at 06:53 UTC
Updated:
30 Jul 2022 at 15:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
catchComment #3
spokjeRTBC if TestBot agrees, and Yay! to less murky worlds in general and specifically for update path tests.
Comment #4
dwwPerhaps premature, but I'm going to RTBC, anyway. I know no committer would actually commit this until this bot comes back green, and it can prove me wrong and NW if it has to... 😉
Thanks!
Comment #5
catchSame patch just without a line missing from the diff *cough*.
Comment #6
dwwHah, whoops. ;) Thanks!
Comment #7
mondrakeMaybe overkill, but I would suggest
so we ensure we only execute for the mysql driver provided by the mysql module? (other modules, even installed, may provide a driver named mysql)
Comment #8
catch#7 might possibly be overkill but it won't do any harm.
Comment #9
spokjeIf we wanna go backport to
9.4.x, looks like we're gonna need a separate patch for it.Comment #10
mondrakeSqlite and PgSql do not have a
hook_requirements()implementation so this looks fine to me, thanksComment #11
dwwJust did a little git archeology. There is no
mysql_requirements()in 9.4.x. That was introduced in #2733675: Warning when mysql is not set to READ-COMMITTED, which wasn't backported to 9.4.x. The earliest core with this bug is 9.5.x. Therefore, bumping the version, and ignoring the fact that #8 doesn't apply to 9.4.x...Thanks,
-Derek
p.s. Also saving credit for all the reviews here.
Comment #15
xjmI didn't understand this issue at first, but after reading the whole hook, this is clearly a bug that it displays its warnings on other drivers. With the information in #10, I agree that the scope is complete here.
Thanks @dww also for the archaeology on why it didn't work on 9.4.x.
Committed to 10.1.x and cherry-picked to 10.0.x and 9.5.x. Thanks!
Comment #16
xjm