https://bugs.kde.org/show_bug.cgi?id=283692
Daniel Vrátil <dvra...@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |CONFIRMED
CC| |dvra...@redhat.com
Ever confirmed|0 |1
--- Comment #5 from Daniel Vrátil <dvra...@redhat.com> ---
In case of database, we report failure to clients when database fails to commit
a transaction. If it finds out that it has run out of disk when it tries to
write the data later on asynchronously is out of our control. However that
should just cause no data to be written and the item simply won't be stored in
Akonadi (clients will "now" about it, but it will disappear on next start).
In case of external payload files, I can see a problem when we run out of disk
space when writing the data to a temporary file or when modifying existing item
(fetching missing parts) - there's no check for successful write. I'll fix
that. Other cases seem to fail correctly when write fails.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
_______________________________________________
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
