Bug #12924
Migration code should not refer to a database name
| Status: | Verified | Start date: | 03/27/2019 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Migration task | |||
| Target version: | Release 2.5.0 | |||
| Google Code Legacy ID: | Tested version: | 2.5 | ||
| Sponsored: | No | Requires documentation: | No |
Description
Migrations 163 and 172 refer to the 'atom' database. This database name should not be specified or errors will occur when these migrations are run against AtoM databases that are not specifically named 'atom'.
Remove references to 'atom' from these migrations.
History
#1 Updated by Steve Breker about 3 years ago
#2 Updated by Steve Breker about 3 years ago
Code review complete - Looks good!
#3 Updated by Dan Gillean about 3 years ago
- Category set to Migration task
- Status changed from New to In progress
- Assignee set to Santiago Collazo
#4 Updated by Dan Gillean about 3 years ago
- Status changed from In progress to Verified
- Assignee deleted (
Santiago Collazo) - Requires documentation set to No