Menu

#33 Problems with "Store covers locally" (MySQL)

closed-postponed
nobody
None
5
2007-05-28
2007-05-09
No

Forum:
http://sourceforge.net/forum/forum.php?thread_id=1731306&forum_id=285354

1) When I switch on "Store covers locally", the (MySQL) database is not loaded after startup.

How to reproduce:
- Enable "Pref|Misc" "Automatically load database on startup"
- Create new MySQL database
- Add 3 movies with covers
- Enable "Pref|Cover" "Store covers locally", choose existing folder for Covers&Queries
(I assume the existing covers are not removed/moved from MySQL into files. But if the existing
Covers in MySQL don't slow it down, this is acceptable. To (re)get the Covers as files, an
IMDb update can be made, which is acceptable, too.)
- Close XMM
- Open XMM
-> BUG: the DB is not loaded, but Entry "Loading DB..." is shown instead.

Correctly, it should _load the entries and show and "X" instead of the image if it cannot be
found in the Covers folders given above.

2) The "Store covers locally" option is not saved.

When I now re-open the MySQL database manually (or was it "close xmm and restart?", the "Store locally options" is not checked, even if I enabled it previously (above). And the covers are loaded again from database and not from directory.

-> "Store covers locally" option should (for the moment) be saved and restoredas global option.

(( 3) local or global options -> to be discussed ))

4) The "Store covers locally" should actually enable & disable (grey out) the Edit field "Cover folder" in "Folders" accordingly.
And for MySQL databases, the Edit field "Queries folders" should always be disabled.
The "Ok" method then should check the folders only if they are enabled.

Matthias

Discussion

  • Matthias Ihmig

    Matthias Ihmig - 2007-05-24

    Logged In: YES
    user_id=921651
    Originator: YES

    (1) seems somewhat solved, but I just again got the "Loading DB" entry instead of the actual entries. Could this be a problem if the mysql database does not answer quickly enough? this does not happen very often - 1 out of 10 perhaps...

    (2) is fixed now.

    (4) With "Store covers locally" disabled, the "Folder" dialog still checks if the directory exists (though it should be ignored.

    Thanks,

    Matthias

     
  • Matthias Ihmig

    Matthias Ihmig - 2007-05-25
    • priority: 5 --> 7
     
  • Matthias Ihmig

    Matthias Ihmig - 2007-05-25

    Logged In: YES
    user_id=921651
    Originator: YES

    Hmm, (1) MySQL DB not loading correctly on startup is still a problem. Now, it didn't work in 5 out of 10 starts. This is a little annoying.

    This happens with MySQL 4.0.x and 5.0.x. (independent of the "Store covers locally" option).
    Though it seems to happen more often on 5.x compared to 4.x

    (4) is now fixed in CVS.

    Again, to (1):
    The output when the DB is _not loaded:
    INFO Loading MySQL:localhost:3306/m3?user=root&password=beinbein
    DEBUG Loading MySQL database
    INFO Connected to MySQL database
    INFO Loads the movies list
    DEBUG sqlQuery:
    SELECT `General_Info`.ID, `General_Info`.`Title`, `General_Info`.`Imdb`, `General_Info`.`Cover`, `General_Info`.`Date` FROM `G
    eneral_Info` ORDER BY `Title`, `Title`;
    DEBUG Database loaded in:1497 ms

    From here, everything seems fine - the only difference to a working start is that the database load actually takes 2439 ms. When it takes only 1497 ms, the entries are not loaded correctly.
    Another hint: in that case, the "Connecting to DB..." dialog is either not shown or disappeared so quickly I didn't see it.

    There seems no fixed way to reproduce - on startup, there is a chance of 50:50 that it works or works not.

    Can you reproduce this?

    Matthias

     
  • Matthias Ihmig

    Matthias Ihmig - 2007-05-28
    • priority: 7 --> 5
    • status: open --> closed-postponed
     
  • Matthias Ihmig

    Matthias Ihmig - 2007-05-28

    Logged In: YES
    user_id=921651
    Originator: YES

    Actually, this problem of the DB not loading correctly is not related to "Store covers locally". Though I still couldn't find a good way to reproduce this bug, and as the other issues are solved I'll close this thread until someone finds a reliable way to reproduce this error.

    Matthias

     
Auth0 Logo