View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008773 | MMW v4 | Install/Config | public | 2011-11-28 20:31 | 2011-12-15 03:18 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0 | ||||
| Target Version | 4.0.1 | Fixed in Version | 4.0.1 | ||
| Summary | 0008773: MM4 doesn't use MM3's custom DBNAME setting on upgrade | ||||
| Description | When upgrading from MM3 to MM4 while user had used a custom DB location with DBNAME in MM3 MM will open with an empty (new) library instead of converting the MM3 database. | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=3&t=62301 http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=62147 http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=62229 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1460 | ||||
|
|
It's because of 0007085. |
|
|
There happened some misunderstandings in implementation of 7085. The details of the DB upgrade process should look like: 1. If MM3 DB is in its default location, it should be moved to the default location of MM4 DB. 2. If MM3 DB is in a custom location, the MM3 converted DB should be stored in the same location. The MM3 DB should be backed up before the conversion to a file MM.DB.MM3. |
|
|
Fixed in 1460 |
|
|
Verified 1461 |
