On Mo, 2011-09-05 at 02:14 +0200, Ove Kåven wrote: > Patrick, what do you make of this "permanent" contact? > > > ~ $ syncevolution --export - goosync addressbook 874 > > BEGIN:VCARD > > VERSION:3.0 > > X-SYNCEVO-QTCONTACTS:Relevance^Relevance^VARIANT^0000000600412e848000000000 > > > > REV:2011-03-18T10:08:51 > > N:;;;; > > END:VCARD > > This empty "contact" seems to be permanent, possibly an artifact of the > database itself.
It could be the artificial "self" contact: http://doc.qt.nokia.com/qtmobility/qcontactmanager.html#selfContactId As far as I know, it is not defined whether that contact can be deleted. Your experiment shows that it can't, probably because it is synthesized from settings on the device. I suggest that you add a check against the self ID and exclude that special contact from syncing. This won't be correct with other QtContact backends (QtContacts-EDS stores a normal contact and marks it as "self"), but Harmattan is now the main (exclusive?) user of the backend, so there's no harm in tailoring it towards that. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
