View Issue Details

IDProjectCategoryView StatusLast Update
0016718MMW 5FileMonitor / Find Missingpublic2020-07-11 01:02
ReporterLudek Assigned To 
PriorityimmediateSeverityminorReproducibilitysometimes
Status closedResolutionreopened 
Product Version5.0 
Target Version5.0Fixed in Version5.0 
Summary0016718: MM5 can upgrade MM4 database when DBName is specified in INI
DescriptionIt seems that when custom DB path is specified in MediaMonkey.ini

e.g.
[System]
DBName=D:\Music Databases\MM.db

Then on update from MM4 > MM5 the MM.DB is updated to MM5 version, this shouldn't happen!!
Details at https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=96581#p469351
TagsNo tags attached.
Fixed in build2260

Activities

petr

2020-06-15 20:15

developer   ~0058559

Fixed

peke

2020-06-16 23:03

developer   ~0058571

As talked offline this bug is partially fixed and in 2257 original MM4 MM.DN from mediamonkey.ini "DBName=c:\Temp\MM.DB" is not updated to MM5, but user also looses custom Path to DB and DBNAME in MediaMonkey.ini

Test case:
1. MM4 install have Custom DBNAME in MediaMonkey.ini to c:\Temp\MM.db
2. Install MM5 -> Import MM4 settings
3. MM5.DB is created in c:\users\AppData\Roaming\MediaMonkey 5\MM5.DB
4. custom Path DBname is removed from Mediamonkey.ini

This fixes original bug, but Expected behavior would be that MM5 Creates c:\Temp\MM5.db and preserve path to custom DB inside Mediamonkey.ini

As original bug is fixed maybe open this behavior we should open new bug I am not sure?

petr

2020-06-18 10:41

developer   ~0058587

Fixed

Ludek

2020-06-18 19:51

developer   ~0058591

Re-opened: this caused a regression: if you delete MM5.DB in Portable folder then it no longer creates the new DB in the Portable folder, but is taking DB from the AppData folder!

petr

2020-06-18 21:12

developer   ~0058594

Fixed

peke

2020-06-20 10:48

developer   ~0058612

Verified 2258

Looks like it is fixed.

Please close after second verification.

Ludek

2020-07-04 08:33

developer   ~0058761

Re-opened, there is still report of this bug not being fixed in 2259 : https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=96581&start=15#p470001

Similar report on MM4 thread: https://www.mediamonkey.com/forum/viewtopic.php?f=6&t=96896

petr

2020-07-04 12:53

developer   ~0058767

For some unknown reason Barry's ini isn't correctly updated so wrong database (MM4) after new start is used. Added code to always use MM5.DB file even when MM.DB is defined in ini file.

peke

2020-07-11 01:02

developer   ~0058879

Verified 2260

I can't replicate using Barry settings or other iterations I can think of.