View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0015858||MediaMonkey 5||DB||public||2019-08-07 08:45||2019-08-31 21:40|
|Priority||immediate||Severity||minor||Reproducibility||have not tried|
|Target Version||5.0||Fixed in Version||5.0|
|Summary||0015858: MM4 vs MM5 database compatibility issues|
|Description||Currently if user defines custom DBName in the INI file and uses the database by both MM4 and MM5 versions simultaneously then MM4 throws dialog that the database is not MM4 compatible.|
We have added workaround (ForceMM4Compatibility flag to the INI file, with this INI options enabled the MM5 > Rebuild database) makes the DB backward compatible with MM4 (see #15151).
This is hard to realize for users though and we agreed that this functionality shouldn't be promoted (see 0015151:0051347)
a) rename mm.db to mm5.db so that such a unintended sharing of single database by MM4 and MM5 instances is not possible (preffered).
EDIT: This is strongly preferred solution, because we should guarantee what we claims:
"Installation of MediaMonkey 5 can be on top of MediaMonkey 4, or independent of MediaMonkey 4. If you run both versions, changes made in one DB will not be reflected in the other."
which is not the case currently!
This solution also covers the case when users installs MM5 portable on top of MM4 portable (to retain MM4 database untouched by MM5)
b) Add '[ ] Force version 4 compatibility' checkbox to 'Manage database' dialog with tooltip '...leads to worse performance...' and makes this checkbox enabled by default when custom DBName location is specified in the INI
|Tags||No tags attached.|
|Fixed in build||2191|