[Kde-pim] Question: Akonadi::TransactionSequence

[Kevin Krammer]

On Wednesday 23 January 2008, Volker Krause wrote:

> No, that's actually a known issue in Akonadi. ItemDeleteJob uses
> transactions internally as well, but the server can't handle cascaded
> transactions yet, libakonadi/itemsync.cpp has the same problem. As a
> workaround, you can use Job instead of TransactionSequence, this requires
> only minimal code changes since Job is a KCompositeJob already. Compared to
> TransactionSequence this has the obvious drawback of not being atomic as
> well as being considerably slower.

Ah, ok. So I tried the worst possible case right at the first attempt ;)

I am currently mostly interested in the queueing so I'll try Akonadi::Job for 
now.

> Of course, fixing the server would be preferred instead ;-) It's basically
> adding transaction counting to DataStore and adjusting the usage of
> inTransaction() accordingly I think.

Maybe when I start to understand better how this communication stuff actually 
works on the lower levels :)

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20080123/35fbb48b/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/