Bug #5492

Task tools:upgrade-sql doesn't seem to work properly

Added by Jesús García Crespo almost 9 years ago. Updated almost 9 years ago.

Status:VerifiedStart date:08/21/2013
Priority:MediumDue date:
Assignee:Jesús García Crespo% Done:


Target version:Release 1.4.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:


How to reproduce:

  1. Clone atom.git (branch 1.x)
  2. Load a 1.3.1 dump into the database (db version should be 92 in settings_i18n id=1)
  3. Run tools:upgrade-sql task
>> backup    Backing up database "atom_1_ubc" to db_20130821145558.sql.bak
>> backup    Database backup complete!
>> upgrade-sql Upgrading from Release 1.1
>> upgrade-sql Upgrading from Release 1.2
>> upgrade-sql Successfully upgraded to Release 1.4.0 v95
That means that the last migration executed was migrations/arMigration0095.class.php.
But if you look at /lib/task/migrate/migrations there's five more classes.
  • 0096 is 2.x only
  • 0097 is 1.x and 2.x
  • 0098 is 1.x and 2.x
  • 0099 is 2.x only
  • 0100 is 2.x only

For some reason arUpgradeSqlTask is not doing its job properly.
The upgrader should bump the db version even when an upgrade is omitted.

Related issues

Related to Access to Memory (AtoM) - Feature #4494: Upgrade arUpgradeSqlTask to decouple major version sql up... Verified 12/21/2012


#1 Updated by Jesús García Crespo almost 9 years ago

  • Status changed from New to Verified

Also available in: Atom PDF