On Thursday, 2013-01-24, Marco Martin wrote: > On Thursday 24 January 2013, Kevin Krammer wrote: > > > if i make the else branch to always execute (ie never using the cache) > > > it's still broken. > > > but, if i disable also QueryCache::insert( statement, mQuery ); > > > so never inserting anything in the cache, all starts to work normally > > > again. ie even just saving those prepared queries somewhere makes it > > > fail. > > > > I don't know enough about the database stuff but it seems we'll have to > > deactivate prepared queries when sqlite is being used (assuming it works > > with PostgreSQL). > > attached patch partially fixes the issue, does it look correct? > still have to try on the device but the agents seem to work correctly after > the first akonadi startup (the first time it runs it still have the > symptoms)
As I said before I don't know a lot about the database part, but as far as I can tell this looks ok. However, I am wondering whether it might not be better to do this with a single if/else in querybuilder, i.e. not access the cache at all if we are on SQLite. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Active mailing list [email protected] https://mail.kde.org/mailman/listinfo/active
