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

List:       kde-pim
Subject:    Re: [Kde-pim] [Akonadi] Merging parttable-optimization branch to master
From:       Luis Felipe Tabera <lftabera () yahoo ! es>
Date:       2013-11-20 20:17:37
Message-ID: 1789690.yENZb5sYjp () mychabol
[Download RAW message or body]

On Wednesday November 20 2013 16:09:14 Daniel Vr=E1til wrote:
> [This only concerns those who use Akonadi from master]
> =

> Hi all (who use Akonadi from master :-)),
> =

> I finally merged Volker's parttable-optimization branch into master [0]
> (wooohoo!). This means that once you update Akonadi, your PartTable schema
> will be migrated. This can take some time (5-10 minutes, depends on how
> large your PartTable is and what DB you use) during which you won't be ab=
le
> to use any Akonadi-based apps (they will show a nice "Please wait while we
> destr^Wmigrate all your PIM data" messsage).
> =

> I successfully tested the migration on all 3 supported backends, but I'd
> still like if you could run Akonadi manually from console after you update
> it so in case of failure we can get some data and I can fix it. I don't
> expect any troubles, but one can never know and I'd like the migration to
> go smoothly once we ship to users in 4.13.
> =

> Thanks for help!

Dan,

I have just compiled master akonadi, mysql backend and around 90K records. =

Migration was "instantaneous". partTypeId column in PartTable and names in =

PartTypeTable seem correct. Everything look smooth.

Luis
_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]