Fix the transaction isolation level error also occuring in core forum module

Created on 17 September 2023, 9 months ago

Problem/Motivation

In Drupal 10.x the module causes an error admin/reports/status
"Transaction isolation level
"READ-COMMITTED
"For this to work correctly, all tables must have a primary key. The following table(s) do not have a primary key: forum_index. See the "setting MySQL transaction isolation level page for more information."

The core forum module has exactly the same error but it appears to be difficult to fix in core.
See https://www.drupal.org/project/drupal/issues/3365945 πŸ› Errors: The following table(s) do not have a primary key: forum_index Needs review

Steps to reproduce

Install the forum module with composer and enable it with drush. View admin/reports/status to view the error.

Proposed resolution

Add a primary key to the forum_index table
Review the core issue at https://www.drupal.org/project/drupal/issues/3365945 πŸ› Errors: The following table(s) do not have a primary key: forum_index Needs review .
The issues limiting resolution of core module error possibly do not apply in the contrib module.

Remaining tasks

Implement a primary key as required.
Review
Commit

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Closed: duplicate

Version

1.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @GrahamShepherd
  • Status changed to Closed: duplicate 9 months ago
  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    It's the same people looking after both so let's not duplicate our efforts

    The blocker in this case is finding time. The patch in the core issue is fine to use if you can't wait

    Thanks for your understanding

Production build 0.69.0 2024