Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Have you thought about a "repair table" button next to the mismatched tables in compare section of the module's ui? It should alter the table's database schema to match the actual drupal schema. If you consider this a good idea i can start implementing that.
Comments
Comment #1
ClearXS CreditAttribution: ClearXS commented(I'm a user and have nothing to do with the development of this module)
First of all module developers should repair their 'faulty' modules or that don't use the proper syntax for different MySQL versions or similar.
So one should report all the errors to the module developers or say receiving the similar error if there is an existing issue for a certain module. I know; the lists of errors/discrepancies can be very extensive and it could take days reporting them all. But that is the only way to urge developers to tackle these problems.
Nothing wrong with your suggestion and in favor of its implementation. But that should be meant more for 'real' errors instead of correcting faulty modules.
Then if I go to MySQL on server level through Cpanel or phpMyAdmin; I thought that I don't get these errors if I check the database. So I can't repair them on that level. The Schema way of doing seems to be a different check than the server check?
Comment #2
drupalok CreditAttribution: drupalok commentedi contacted wapnik and he said that he would not be implementing this, as there was no feedback.
well I think having a repair button would be awesome... so hands up if you would like to see this feature! :)
Comment #3
giorgio79 CreditAttribution: giorgio79 commentedSuch a button would be awesome :) Even updb did not help in fixing these schema differences.
Comment #4
fullerja CreditAttribution: fullerja commentedI would also really like to see this feature
Comment #5
loopy1492 CreditAttribution: loopy1492 commentedIt would be delicious, though the offending Module developers really should fix their stuff as well.
Comment #6
Angry Dan CreditAttribution: Angry Dan commentedI'm assuming that this would be as simple as calling db_change_field() on each of the broken entries?
Comment #7
Dave ReidI am feeling that this really shouldn't be added to this module either. I feel like it should be used as a tool to report the issues back to the modules and fix those issues there. Adding repairability here might cause conflicts or issues when the actual modules are updated with fixes? Do we add or remove columns? Can we tell the difference between mismatched schema and a site that just hasn't run update.php yet? There are a lot of unknowns and things that could go wrong if this functionality was added.
Comment #8
blogers CreditAttribution: blogers commentedi have missmatch tables its true o false the warning ?
Comment #9
blogers CreditAttribution: blogers commentedi have missmatch tables its true o false the warning ?
Comment #10
joachim CreditAttribution: joachim as a volunteer commented#2571659: Fix missing tables [patch attached] is a similar issue, with a patch that adds a Drush command for this.
I'm tempted to close both as wontfix, based on Dave Reid's comment in #7.