Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VOTE-906: Add documentation about mysql configuration limitations. #628

Merged
merged 2 commits into from
Mar 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/backend.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,3 +85,14 @@ Review the details in composer.json file under `extra.patches` additionally look
## Migration
Instructions for updating and running migration scripts.

## Database - Mysql
The site utilizes Mysql for its database.

### Limitations
Through its implementation via Cloud.gov there are limitations over what is configurable for Mysql.

#### Setting the MySQL transaction isolation level
Issue: The recommended database transaction isolation level is READ COMMITTED vs REPEATABLE READ.
Description: In addition to being unable to configure Mysql, the alternate solution of setting the isolation level via the database configuration within the settings.php file is not a recommended approach as it sets the isolation level upon each page load which isn't optimal.
Impact: Low
Source: https://www.drupal.org/docs/getting-started/system-requirements/setting-the-mysql-transaction-isolation-level#s-other-methods-to-change-the-transaction-isolation-level