Bug #832
closed
bug fix #871 breaks upgrade for those with processingdb table in projectdb
Added by Anchi Cheng over 14 years ago.
Updated about 14 years ago.
Affected Version:
Appion/Leginon 2.0.2
Description
Found this bug while testing database sent by Nogales lab. We only know reliably that Nogales and Skaggs labs have appion 1.0 running and the latter has already done the upgrade, so it is not as critical to put it to the branch but I do recommend it. The update Wizard need to check if processingdb exists in initTableReport.php If it does, it should not add processingdb table schema. The bug makes processindb have both db column and appiondb column and schema-13713.ps could not rename column when the destination exists.
- Status changed from Assigned to In Code Review
- Assignee changed from Anchi Cheng to Eric Hou
fix with r14706 by moving processingdb table schema xml to a new file.
Testing:
1. can use /ami/amishare/myamiSampleDatabases/leginon_1_6_appion_1_0_dbem_1_5_proejct_1_2_databases for positive test.
1a. Go through myamiweb/setup wizard.
After setup wizard finish, proecssingdb table should not have a column named appiondb.
1b. Go through the dbschema upgrade python scripts.
No scripts should fail. It may not find all processingdb, though.
2. can use /ami/amishare/myamiSampleDatabases/leginon_1_6_dbem_1_5_0_project_1_1_databases for negative test.
Testing procedure is the same.
- Status changed from In Code Review to In Test
- Assignee changed from Eric Hou to Amber Herold
- Assignee changed from Amber Herold to Eric Hou
- Status changed from In Test to Closed
double confirm with Anchi.
Case Close.
Also available in: Atom
PDF