T7846: akonadi > MySQL ERD Review

[Pablo Sanchez]

pablo added a comment.


  > We can normalize the [CollectionAttributeTable].type column by moving the key names to their own table like we do in [PartTable] as suggested in the link, but that's about all that I could find there that would apply in our case.
  
  The above suggestion is what I would first suggest.
  
  For this discussion, let us call this new table **[CollectionAttributeTableType]** (boy I am clever!)  The next question is whether this new table's domain is shareable by all of PIM or does each **[ResourceTable]]** get its own set of values.  I don't know, I'm just asking ... :)  .. and yes, I'm slowly winding my way through the per-table doc today (which is why I can even offer the table name **[ResourceTable]**!)
  
    pablo@ on akonadi
    12:37:11 27> select distinct type from collectionattributetable;
    +----------------------------+
    | type                       |
    +----------------------------+
    | AccessRights               |
    | ENTITYDISPLAY              |
    | SpecialCollectionAttribute |
    +----------------------------+
    3 rows in set (0.01 sec)
    
    pablo@ on akonadi
    12:37:48 28> select type, count(*) from collectionattributetable group by type;
    +----------------------------+----------+
    | type                       | count(*) |
    +----------------------------+----------+
    | AccessRights               |        5 |
    | ENTITYDISPLAY              |        9 |
    | SpecialCollectionAttribute |        7 |
    +----------------------------+----------+
    3 rows in set (0.01 sec)

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

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