Re: Sqlite akonadi transaction mode fix
Hey,
as martin already mentiond: SQLite is really not the preferend database
backend. I played around with it for some time and it triggers randomly
Database Errors. The base problem, is that sqlite only allows one writing
thread, that's why you get deadlocks with sqlite.
I'm glad if I can assits you fixing the sqlite issues. I'm a upstream
developer, too. If there are any questions, just ask.
IMO sqlite really do not fit for akonadi, so i would recommend to switch to
mysql or postgres.
Regads,
sandro
--
Am Mittwoch, 21. Januar 2015, 09:49:18 schrieb David Goodenough:
> I use KdePIM and thus akonadi with SqLite. I am running unstable and am
> up to date with fixes.
>
> Looking in the KDE bug database I found:-
>
> http://osdir.com/ml/kde-commits/2014-07/msg02228.html
>
> which seems to address the repeated dialog boxes I get while filters run on
> my mailboxes, and the log messages of which:-
>
> DATABASE ERROR:
> Error code: 6
> DB error: "database is deadlocked"
> Error text: "database is deadlocked Unable to fetch row"
> Query: "UPDATE PimItemTable SET atime = ? WHERE ( ( PimItemTable.id = ? )
> )"
>
> is an example. All the errors I get currently are deadlock errors.
>
> I don't think this fix is in the current build, and I realise that Debian is
> getting ready for a new release and thus it is unlikely that this fix will
> be able to be slotted in any time soon. Can I simply get the source, add
> this one patch and rebuild, or is it more complicated. Also which
> package(s) would I have to rebuild? Is it just akonadi-backend-sqlite?
>
> David
Reply to: