tools:upgrade-sql failing on multiple client SQL dumps
|Target version:||Release 2.3.0|
|Google Code Legacy ID:||Tested version:||2.3|
Multiple client SQL files I tried to upgrade to 2.3 give the following error:
Column already exists: 1060 Duplicate column name 'download_path'
I think we should check for the column's existence too before creating it. I'm not sure why so many clients already had that column or whatever, they were using 2.1 I believe...
arMigration0130.class.php is the culprit. Maybe we can do something like so: http://stackoverflow.com/a/3242110
#4 Updated by Mike Gale about 6 years ago
- Assignee changed from Mike Gale to Mike Cantelon
That's indeed weird how only certain migrations give us problems. Somehow the tables / columns get into client database schemas before we create proper migrations for them? Or somehow their db versions get out of wack? At any rate, this extra check looks good to me.