Data integrity error: some hashes recorded as babel_source lack status in babel_source_status table

Created on 18 July 2025, 3 months ago

Steps to reproduce

  1. Install Drupal with minimal profile: drush si minimal -y
  2. Enable Babel drush en babel -y
  3. Count the records with unique hashes in "babel_source": SELECT COUNT(innerQuery.*) FROM (SELECT DISTINCT hash FROM babel_source) innerQuery. On my system with the current core, this is 75.
  4. Count the records with unique hashes in "babel_source_status": SELECT COUNT(innerQuery.*) FROM (SELECT DISTINCT hash FROM babel_source_status) innerQuery. On my system with the current core, this is 41.

Without involving the UI translation (these are only configs), we have only config strings recorded so far, some of them have records, some of them don't.

Proposed resolution

Find the cause and fix this integrity issue.
Maybe, rethink how statuses are stored. Imho they should belong to a source rather than to a string + context pair.

Remaining tasks

User interface changes

API changes

TBD

Data model changes

TBD

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

🇭🇺Hungary huzooka Hungary 🇭🇺🇪🇺

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

Merge Requests

Comments & Activities

Production build 0.71.5 2024