url_alias NID index

Created on 15 October 2012, over 11 years ago
Updated 30 July 2023, 11 months ago

I poked around but didn't see this addressed elsewhere - why is url_alias still indexed by a text string ('node/NID')? Every query to this table needs to concatenate a string value prior to the join, so joins are incredibly inefficient. I can understand needing a special case for non-node storage, but when making editorial tools, Views Bulk Operations, or even just large output sets, screen load / query times are just horrible when paths are included in the output.

It would be much better if url_alias had the same entity_type/entity_id/bundle fields that other tables did, or better still, used Entity API for its data storage. I'd even be willing to do this myself - but I wanted to check in with the community on acceptance / desire before starting it.

✨ Feature request
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component
PathΒ  β†’

Last updated 6 days ago

  • Maintained by
  • πŸ‡¬πŸ‡§United Kingdom @catch
Created by

πŸ‡ΊπŸ‡ΈUnited States crobinson

Live updates comments and jobs are added and updated live.
  • DrupalWTF

    Worse Than Failure. Approximates the unpleasant remark made by Drupal developers when they first encounter a particular (mis)feature.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024