database refreshing

[Llorean]

The icon in the upper corner represents ALL disk access. You might be seeing it for database scanning. Or for dircache scanning. Or because you're browsing and so it accesses the disk, or music is buffering, etc...

[pizza4me]

yeah, I do understand the icon function.  I don't understand what it's doing when it says "committing database" on startup.

The database is very much not completely updated when "committing database" hits 9/9.

[MarcGuay]

The answer probably lies in here:

http://svn.rockbox.org/viewvc.cgi/trunk/apps/tagcache.c.

Or you could pop into IRC and look for Slasheri (spelling?).

[pizza4me]

yeah...probably.

thanks for your help anyway

[Chronon]

The database is very much not completely updated when "committing database" hits 9/9.

Can you clarify what you mean by that?  I thought you got the database to update properly by allowing it to finish scanning before shutting down and booting again.

[MarcGuay]

I was under the impression that although the "committing database" splash had completed, he had to wait for the disk activity icon to stop before the database was actually finished doing it's work.  I seem to remember running into this myself a long time ago when I first tried the database.

[Chronon]

I hadn't read pizza4me's messages that way, I guess.   

I just freshly initialized my database.  I rebooted, waited for it to count up through 9/9 and load the main menu.  I immediately went to the database and see what looks like a complete listing.  What evidence should I see that it didn't update properly?

[pizza4me]

I notice it esp. when I take out a larger card, and reboot with a different large card.  If you go straight to the database after reboot, you'll see files from the old card and not all the ones from the new card - because it hasn't had time to refresh everything.

So even though the Committing Database splash goes through 9/9 it actually hasn't refreshed everything.

[Chronon]

But if I return to the database once the initial disk access has ceased then I will see the proper listing?  I just want to be clear on the steps since I'm not familiar with this behavior.

[MarcGuay]

If the answer to that question is "Yes", which I think it will be from the previous posts, I'd hypothesize that the "committing database" splash is referring to it having completed adding the new songs to the database, but not having removed the old ones from it (note: this only happens with dircache enabled).

[Llorean]

As far as I know, "Committing" is a process based on data from the last time your player was booted. Basically, it's part of the initialization process, not the updating process.

If you swap MicroSD cards while the player is turned off, if a commit happens at boot it shouldn't include any data from the new card and after the boot further updating will need to happen.

[MarcGuay]

That makes sense.  It's retrieving the data from the *.tcd files and building the database with them.  I stand by my earlier statement, then, that it would be a nice feature to tell the user when the updating is complete.

[Chronon]

If you swap MicroSD cards while the player is turned off, if a commit happens at boot it shouldn't include any data from the new card and after the boot further updating will need to happen.

And an additional database commit will be needed after turning the player off and back on again. 

[pizza4me]

so why doesn't the database "commit" every time the player starts?  When I started this post I was assuming that it was the result of selecting Auto Update.

[Chronon]

It should only commit if there are changes to the media on the player that were detected the last time Rockbox ran.