I just took a quick look at the LMS branch and noticed something strange
in the database changes regarding timestamps.
As far as I can see it has:
- tracks.added_time: The time when a track was added to the library
- tracks_persistent.added: The modification time when a track was added
initially to the library.
Is there a reason why we need both tracks_persistent.added and
tracks.added_time ?
I'm guessing tracks.added_time doesn't survive a rescan, in that case
it would feel better to just use tracks_persistent.added which does
survive a full rescan and change it so it's set using now() instead of
the modification time. Or is there some intention with this so we
really want a tracks.added_time that doesn't survive a full rescan ?
I believe the reason tracks_persistent.added was included when we
created the tracks_persistent table was to make it possible to make a
"New Music" menu which showed albums in the order they were added to
the library instead of showing them in the order they have been last
tagged/modified.
--
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=87579
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
