Contrib.social

schema_version updates in spite of failure

Open on Drupal.org →
Created on 13 January 2009, almost 16 years ago
Updated 31 July 2024, 5 months ago

Hi,

I've decided to make this priority "critical", but downgrade if you disagree. I have two database users - one with MySQL "table alter" permissions and one without. I need to remember to switch my connection user to the correct one before running update.php but this is the restriction IT place on me, so that's the way it must be.

Today I was updating Imagefield and Imagecache, both of which had ALTER queries. I used the wrong user and got a FAILED messages at the end of the update run. No problem, I thought - I'll pick the correct user then run update again. But the second time update did nothing. I checked the system table and the schema_version column has been updated to latest, even though the update actually failed to complete properly!

Surely this is wrong? =(

🐛 Bug report
Status

Active

Version

7.0 ⚰️

Component
Database update  →

Last updated 3 days ago

No maintainer
Created by

🇫🇷France greg.harvey

Live updates comments and jobs are added and updated live.
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.

  • Comment 8 months ago →
    🇮🇹Italy apaderno Brescia, 🇮🇹
  • Comment 5 months ago →
    🇺🇸United States dww

    update.module is for the available updates report at admin/reports/updates. This is a bug report for the "database update system" and update.php.

  • Comment 5 months ago →
    🇮🇹Italy apaderno Brescia, 🇮🇹

    I was looking for the component that replaced system update, but I didn't realize that was database update system. 😅

  • Status changed to Closed: outdated 5 months ago
  • Comment 5 months ago →
    🇮🇳India sukr_s

    Checked on 11.x. This issue is fixed. If an update fails, subsequents updates don't run.

  • Status changed to Active 5 months ago
  • Comment 5 months ago →
    🇮🇹Italy apaderno Brescia, 🇮🇹

    This issue has not been fixed for Drupal 7. Drupal 7 issues are not closed because they are fixed in Drupal 11.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024