Contrib.social

Changea DB schema for TrafficRegistry?

Open on Drupal.org →
Created on 10 April 2025, 3 days ago

Problem/Motivation

I did a code review on this module and was wondering about the reason for the current DB-schema for the TrafficRegistry. Cache tags are a separate table (purge_queuer_url_tag) and the IDs for this tables are stored as a "serialized" string in purge_queuer_url.tag_ids. What is the reason to store it like that?

I thought the cache tags could be stored as text along with the URL, similar to the \Drupal\Core\Cache\DatabaseBackend in an single table?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Active

Version

1.0

Component

Code

Created by

🇩🇪Germany webflo

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

Comments & Activities

  • Issue created by @webflo
  • Comment 3 days ago →
    🇩🇪Germany webflo
  • Comment 2 days ago →
    🇳🇿New Zealand ericgsmith

    Hello 👋

    I can't offer any insights to the original design - I became a maintainer in 2023 in order to get a D10 release out - and as part of that process I never heard back from @nielsvm so I am unsure if they would see this.

    My focus as maintainer since this has been trying to progress issues that are either RTBC or relevant to the projects I work on. So as such if there is benefit to improve here and somebody is willing to do the work (including tests to prove it works and that its beneficial) I would support it and be available to review / commit etc.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024