JJZolx;578170 Wrote:
> I'm not convinced that it buys you much either. You still have to deal
> with tracks that change on disk. Unless you completely rebuild the
> main database from scratch using that raw data each time a file
> changes, then you you still have the dependencies and stale records to
> remove. You can't completely rebuild the whole database every time a
> single track changes. Moreover, the current approach doesn't require
> going back out and rereading any data from any other files beyond those
> that have changed, so having the raw data available doesn't save you
> from doing any disk reads.
If I remember correctly I think the purpose of a twp phase database was
to avoid having to do a full rescan when you have changed some setting
that usually requires it. There was a lot bigger need for this with the
new schema approach as you may want to re-configure the schema without
having to do a full rescan. I'm pretty sure it wouldn't make
incremental rescans any faster.
However, it would probably simplify the logic a bit since the logic for
the second phase can be exactly the same for a full and incremental
rescan. This will also ensure that a full rescan always gives the same
result as an incremental rescan if we assume that the phase one
database has fresh tag values.
--
erland
Erland Isaksson ('My homepage' (http://erland.isaksson.info))
(Developer of 'many plugins/applets'
(http://wiki.slimdevices.com/index.php/User:Erland). If my answer
helped you and you like to encourage future presence on this forum
and/or third party plugin/applet development, 'donations are always
appreciated' (http://erland.isaksson.info/donate))
------------------------------------------------------------------------
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=82096
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
