Hi Nancy, If you have users that run the updates more than once either:
1. There is a bug in Drupal causing updates to be run more than once. 2. Users are selecting the update to be re-run of their own accord. 3. Users are selecting the update to be re-run for some other reason. So: 1. Is a fairly serious issue. 2. Is their fault. 3. depends who is telling them to do it. Regards Steven Jones ComputerMinds ltd - Perfect Drupal Websites Phone : 0121 288 0434 Mobile : 07951 270 026 http://www.computerminds.co.uk 2009/5/15 Nancy Wichmann <[email protected]>: > Chris Johnson wrote: >> I think it would be cleaner and clearer to simply find a way to record >> which update had completed > > One would think that checking the "schema_version" in the system table would > be an easy way to do this. Unfortuantely, update.php is too "smart;" when > one selects, for example, update 6113 to run, update.php resets the system > table to 6112 before the hook_update_6113 runs, so checking the table > doesn't work. Much as I hate to do it, I guess the only way to do this is to > set a variable. > > Nancy E. Wichmann, PMP > Injustice anywhere is a threat to justice everywhere. - Martin L. King, Jr. > > > > No virus found in this outgoing message. > Checked by AVG - http://www.avg.com > Version: 8.0.176 / Virus Database: 270.12.31/2116 - Release Date: 5/15/2009 > 6:16 AM > >
