https://bugs.kde.org/show_bug.cgi?id=305543
--- Comment #9 from Daniel Vrátil dvra...@redhat.com ---
I committed the files in /server/src/search stuff accidentally, the real fix is
the +52 in querybuilder.cpp :-)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=305543
Daniel Vrátil dvra...@redhat.com changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever
https://bugs.kde.org/show_bug.cgi?id=305543
Daniel Vrátil dvra...@redhat.com changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=305543
--- Comment #8 from Maciej Mrozowski reave...@gmail.com ---
Wow, so many changes. Was updating item access time actually worth it?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=305543
Daniel Vrátil dvra...@redhat.com changed:
What|Removed |Added
CC||dvra...@redhat.com
---
https://bugs.kde.org/show_bug.cgi?id=305543
--- Comment #4 from Maciej Mrozowski reave...@gmail.com ---
Relation CollectionPimItemRelation exists in my case, still query in question
fails.
UPDATE PimItemTable SET atime = :0 WHERE (
CollectionPimItemRelation.Collection_id = :1 AND (
https://bugs.kde.org/show_bug.cgi?id=305543
--- Comment #5 from Maciej Mrozowski reave...@gmail.com ---
Btw, it seems related code is below:
void FetchHelper::updateItemAccessTime()
{
Transaction transaction( mConnection-storageBackend() );
QueryBuilder qb( PimItem::tableName(),
https://bugs.kde.org/show_bug.cgi?id=305543
Maciej Mrozowski reave...@gmail.com changed:
What|Removed |Added
CC||reave...@gmail.com
---
