T7846: akonadi > MySQL ERD Review

[Daniel Vrátil]

dvratil added a comment.


  > This table is used, so that each resource can save additionla data for a collection, so far I know it is mostly requested via collectionid and a given type. Aka:
  >  `select value from CollectionAttributeTable where type="type" and collectionId=?`
  
  The most common query is actually
  
    SELECT collectionId, type, value FROM CollectionAttributeTable WHERE type IN (....) AND collectionId IN (....) ORDER BY collectionId ASC
  
  > One type is defined in one attributeclass see. src/core/*attribute.(cpp|h) and than src/core/protocolhelper.cpp and src/core/attributefactory.cpp doing the magic.
  
  Where the types are defined in code is irrelevant, we are looking into how to deal with this on the DB level. The implementation should not stand in the way of db optimization (otherwise we wouldn't get anywhere :-))

TASK DETAIL
  https://phabricator.kde.org/T7846

To: pablo, dvratil
Cc: knauss, dvratil, kde-pim, pablo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20180205/7aeb4ce7/attachment.html>