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

Fields DetailUri and LinkedDetailUris are not part of default schema, other than advertized

    XMLWordPrintable

Details

    • 936d69600335b16db87ffd74d09cb28f51e21ed4

    Description

      While the API dox of QContactDetail mentions the fields DetailUri and LinkedDetailUris to be "common to all details" [0], like the field Context is "common to all details" [0], these fields are not listed in the default schema definitions as returned by QContactManagerEngine::schemaDefinitions(int version) [1]. There for almost each detail the Context field gets added (fields.insert(QContactDetail::FieldContext, f);), but for no detail the fields for DetailUri and LinkedDetailUris.

      [0] http://doc.qt.nokia.com/qtmobility-1.2/qcontactdetail.html#details
      [1] https://qt.gitorious.org/qt-mobility/contacts/blobs/c3fc8dd/src/contacts/qcontactmanagerengine.cpp#line793

      This seems pretty inconsistent, or even wrong. At least this should be mentioned somewhere in the API dox. We just had no fun while discovering this during our work on the qtcontacts-tracker implementation.

      Seems the qtm unit tests also currently miss to cover storing and fetching of these fields in the engines.

      Also, at least the type and displaylabel details do not have a context, so the API dox is wrong about that as well.

      Please help and improve/fix this

      Attachments

        Activity

          People

            jukukkon Juha Kukkonen
            kossebau Friedrich W. H. Kossebau
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: