I don't have the insight why upstream chose mysql, but I think it is because of the scalability. Akonadi is meant to be unified storage for mails, calendars, notes, contacts... actually it could store pretty much anything. Amarok 1 is using sqlite by default, which caused a lot of problems with a large music collection (>15k) in Akonadi you can pretty easy have that amount of data, so that probably supported the decision as well. On a side note I'd like to mention that the original idea was to use mysql embedded, but upstream decided against it because it doesn't work properly in mysql 5.0. However Amarok is using mysql that way, so maybe we could convince Akonadi upstream to do the same.
So the first option is rather impossible because there wouldn't be enough QA IMHO, the second one isn't either because KDEPim is supposed to start using Akonadi in the upcoming 4.2 release (which is going to be shipped in 9.04), the third option seems most sensible right now. -- [jaunty] kubuntu-desktop drags in mysql-server-5.0 https://bugs.launchpad.net/bugs/304010 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to akonadi in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
