[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 125955] ability to store separate personal information using a
From:       rich () hq ! vsaa ! lv
Date:       2006-04-25 7:46:44
Message-ID: 20060425074644.11947.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=125955         




------- Additional Comments From rich hq vsaa lv  2006-04-25 09:46 -------
i proposed to separate only statistical data, so in case a tag is modified, it would \
be modified in common tables, thus the change would be propogated to all users.

why the need for a single collection with separate stats ?
if several people are using a single collection, that gives the benefits of tag \
fixing to all the users. this includes song data corrections, compilation status and \
preferably album covers. also collection rescanning can be done once for all users.

currently each user has to manage separate collection, which involves rescanning it \
for every instance of amarok, download album covers separately etc. this might be \
acceptable with small collections, but once they pass hundred gb, it is pretty \
annoying and takes a lot more resources.

note that postgres howto includes information on making this possible with db means, \
but having a unified approach would allow also mysql users to use this feature.


[prev in list] [next in list] [prev in thread] [next in thread]