View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004871 | MMW v4 | Properties/Auto-Tools | public | 2008-10-04 11:35 | 2008-10-05 21:14 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.1 | ||||
| Summary | 0004871: "Clear database..." does not actually clear all database | ||||
| Description | As reported here: http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=2338 The tables that are actually cleared are only the Songs, Artists, Albums, Medias and Playlists, but there are a lot of other tables that should be cleared like Played, Podcasts, PodcastsEpisodes, ArtistsAlbums, Geres, GenresSongs, Filters, Folders etc. etc. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1188 | ||||
|
|
I added many others tables that have not been actually cleared. Reminder sent to Jiri in order to review whether they all should be cleared, but i think that the current approach is quite dangerous and hard to maintain, I guess that we should delete whole database (not just tables) and create all tables again via CreateNewMM3Database() from NewDBCreate.pas unit, am I right? |
|
|
Reminder sent to: jiri |
|
|
Most tables are linked to Songs and using DELETE trigger on Songs are also cleared (like ArtistsSongs, GenresSongs, etc.), i.e. it shouldn't be necessary to clear them on ClearDatabase() action. As for full recreation of DB, there could be some problem, e.g. scripts can have some custom tables, etc. We would need to introduce some new mechanism for this, so let'd defer this way. |
|
|
Ok, If you think that custom tables created by some scripts should not be deleted by performing this action then yes, we should leave the current solution. Fixed 1188. |
