Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
#2733675: Warning when mysql is not set to READ-COMMITTED added a warning when the isolation level is not READ-COMMITTED. The link is not accessible as the text is meaningless and the information appears and disappears. This information should always be present but the severity should change.
Proposed resolution
Update mysql_requirements() to always add the transaction isolation level and change the severity depending on the level.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 3291949-3.patch | 3.88 KB | alexpott |
| #3 | 2-3-interdiff.txt | 3.36 KB | alexpott |
| #2 | 3291949-2.patch | 4.54 KB | alexpott |
Comments
Comment #2
alexpottComment #3
alexpott@catch wants to keep the warning. I think we still need to make some improvements.
The link is not accessible since the link text makes no sense and we should always display the requirement even if it is set to READ COMMITTED. Having this information here means people have a chance of learning about why it is important and the fact it is different in different environments.
I wonder if we should mention that REPEATABLE READ is supported. Not sure.
Comment #4
daffie commentedWhen the isolation level is set to "READ COMMITTED" a message that everything is OK.
Testing has been added for the message.
For me it is RTBC.
Comment #6
catchCommitted/pushed to 10.1.x and cherry-picked back through to 9.5.x, thanks!