Make more explicit in Schema::changeField() which indexes need to be rebuilt

Created on 1 August 2013, almost 11 years ago

Updated 16 February 2023, over 1 year ago

Schema::changeField() shows the following note.

IMPORTANT NOTE: To maintain database portability, you have to explicitly recreate all indices and primary keys that are using the changed field.

I would make it more explicit by adding a sentence, changing that note to the following one.

IMPORTANT NOTE: To maintain database portability, you have to explicitly recreate all indices and primary keys that are using the changed field. Only those indexes that directly use the changed field need to be dropped and re-added.

📌 Task

Status

Needs work

Version

10.1 ✨

Component

Documentation →

Last updated about 10 hours ago

No maintainer

Created by

🇺🇸United States Clearbrook

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment over 1 year ago →
🇺🇸United States Amber Himes Matz Portland, OR USA
The patch in #13 does contain the original suggestion. The comment in #7 is never (in 10 years) clarified with a patch or actual suggestion, so I'm ignoring that. I'm going to submit it for re-testing in current versions to see if it still applies and then I'm OK with it moving forward.
Status changed to Needs work over 1 year ago8:31am 16 February 2023
Comment over 1 year ago →
🇮🇹Italy apaderno Brescia, 🇮🇹
Comment over 1 year ago →
🇮🇳India pooja saraah Chennai
Rerolled patch against Drupal 10.1.x
Attached patch
Comment over 1 year ago →
🇮🇹Italy apaderno Brescia, 🇮🇹

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024