View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008782 | MMW v4 | DB/FileMonitor | public | 2011-11-29 23:27 | 2011-12-15 03:15 |
| Reporter | Ludek | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0 | ||||
| Target Version | 4.0.1 | Fixed in Version | 4.0.1 | ||
| Summary | 0008782: SQL error when upgrading from version 3.0 to version 4.0 | ||||
| Description | If a user upgrades from version 3.0 or lower to version 4.0 then this SQL error appears: "Drop Trigger update_songs_artist: no such trigger:update_songs_artist (1,1)" This error does not happen when upgrading from 3.2.x to 4.0 The workaround is to upgrade to version 3.2.5 at first and then upgrade to 4.0.0 | ||||
| Steps To Reproduce | 1. Delete both MM.DB files (in MM3 and MM4 locations) 2. Install e.g. version 3.0.3 from here: http://fs34.filehippo.com/8246/115e2503b63945d6b88db760aa2f3ca7/MediaMonkey_3.0.3.1173.exe 3. Run it in order to create DB 4. Install version 4.0 and run it => SQL error appears | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=62299#p320554 http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=14095 http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=14113 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1460 | ||||
|
|
Fixed in build 1460. |
|
|
Ludek, for clarification, if the user has this problem with MM 4.0, does the problem go away when upgrading from MM 4.0 to MM 4.0.1? |
|
|
This problem goes away by - upgrading to version 3.2.5 at first and then to 4.0.0 - upgrading to 4.0.1 directly, but 4.0.1 hasn't been released yet |
|
|
Verified 1461 |
