Active
Project:
URLs queuer
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 Apr 2025 at 08:33 UTC
Updated:
11 Apr 2025 at 01:57 UTC
Jump to comment: Most recent
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?
Comments
Comment #2
webflo commentedComment #3
ericgsmith commentedHello 👋
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.