https://bugs.kde.org/show_bug.cgi?id=338658
--- Comment #96 from Steven Haigh <net...@crc.id.au> ---
Thanks for the additional info - would it be too much to ask to find the
previous patch?
I guess the idea was along the lines of a LIMIT 1 in scenarios where more than
one result would kill the world.
Ideally, this could be a runtime fix - and the fsck ability of akondactl could
remove duplicate entries.
I still use this code in the SQL tab of akonadiconsole:
DELETE FROM pimitemtable WHERE pimitemtable.id in (
SELECT id FROM (
SELECT id FROM pimitemtable
LEFT OUTER JOIN (
SELECT MIN(pimitemtable.id) as RowId, pimitemtable.remoteId,
pimitemtable.collectionId FROM pimitemtable GROUP by pimitemtable.remoteId,
pimitemtable.collectionId
)
as KeepRows ON pimitemtable.id = KeepRows.RowId
WHERE KeepRows.RowId IS NULL
) AS foo
)
Source:
https://wiki.meurisse.org/wiki/Workarounds#Kmail:_Multiple_merge_candidates.2C_aborting
This seems to resurrect things until it occurs again.
Still annoying and really needs to be fixed.
--
You are receiving this mail because:
You are watching all bug changes.
