Uploaded image for project: 'Qt Mobility'
  1. Qt Mobility
  2. QTMOBILITY-1738

API dox for saving relationship(s) does not specify that relationships should be updated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: P4: Low P4: Low
    • None
    • 1.2.0
    • Contacts
    • None

      Looking at the implementation of QContactMemoryEngine and the expectations of tst_QContactManager::relationships()°°° I find the API dox of QContactManagerEngine::saveRelationships(...)° and QContactRelationshipSaveRequest°° to be way incomplete:

      • does not mention that second contactId could have an empty managerUri and by this mean to also be from the local manager
      • does not mention that if the second contactId has an empty managerUri that one should be set to the one of the local manager in the passed relationship object (i.e. the passed relationship(s) should be updated with that)

      Please add to the API dox about this behaviour, so it is officially specified. Until now qtcontacts-tracker had a implementation not matching this, so tst_QContactManager::relationships() fails for it.

      ° http://doc.qt.nokia.com/qtmobility-1.2/qcontactmanagerengine.html#saveRelationship
      °° http://doc.qt.nokia.com/qtmobility-1.2/qcontactrelationshipsaverequest.html
      °°° https://www.qt.gitorious.org/qt-mobility/contacts/blobs/master/tests/auto/qcontactmanager/tst_qcontactmanager.cpp#line3288

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            satu.m.makela satu makela
            kossebau Friedrich W. H. Kossebau
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:

                There are no open Gerrit changes