Fixing things Akonadi doesn't with some SQL-fu

[Jerome Yuzyk]

So while I wait for Akonadi to reliaby do whatever magic was promised us long 
ago it still left me with a buggered database that makes every new mail pick-
up an adventure, including this folder. Hopefully there are at least plans to 
make akonadictl fsck actually fix things some day so it's easier to wait.

Every time KMail gags on a "Retrieving..." and I shut it down and have to 
eventually kill a lingering kmail process and then cleanup after akonadictl 
stop crashes I run akonadictl fsck and it gives me the usual list of

Item "122837" has no RID.
Item "138602" has no RID.
Item "170068" has no RID.
Item "201887" has no RID.
Item "201888" has no RID.
Item "201889" has no RID.
Item "201892" has no RID.

which has been growing.

I've gone into akonadiconsole and even though it crashes too when trying to 
view one of those no-RID Items (all KMail messages) I can see that in fact the 
RID column is empty for the Items that were flagged.

So how could I manually clear out those Items, either with akonadiconsole or 
the SQL cli, or even PHPMyAdmin? I've read through https://techbase.kde.org/
KDE_PIM/Akonadi/Development_Tools#Access_to_the_Server_Database but before I 
dive in on my own has anyone else ever done any Akonadi DB surgery using any 
of these methods? I have some SQL DB experience, and have hand-edited MythTV 
SQL tables using PHPMyAdmin before, and it's worth learning more so I can keep 
using KMail.

Has anyone attempted such a thing?