SchemaSpy Analysis of zot - Anomalies 2015-11-04 - Hubzilla database schema with some corrected cross-table relationships supporting decentralized publishing. Haakon Meland Eriksen. | Generated by SchemaSpy |
Things that might not be 'quite right' about your schema: |
|
-
Columns whose name and type imply a relationship to another table's primary key:
Child Column Implied Parent Column addon.id notify.id app.id notify.id attach.id verify.id auth_codes.client_id clients.client_id auth_codes.id tokens.id config.id verify.id config.k cache.k conv.id verify.id event.id notify.id fcontact.id verify.id ffinder.id verify.id fserver.id notify.id fsuggest.id notify.id group_member.id verify.id groups.id verify.id hook.id notify.id item.id verify.id item_id.id verify.id likes.channel_id channel.channel_id likes.id verify.id mail.account_id account.account_id mail.channel_id channel.channel_id mail.id verify.id manage.id notify.id pconfig.id notify.id pconfig.k cache.k photo.id verify.id profdef.id verify.id profext.channel_id channel.channel_id profext.id verify.id profext.k cache.k profile.id notify.id profile_check.id verify.id register.id verify.id sign.id verify.id spam.id notify.id sys_perms.id verify.id sys_perms.k cache.k tokens.client_id clients.client_id xconfig.id verify.id xconfig.k cache.k xign.id verify.id -
Tables without indexes:
Anomaly not detected -
Columns that are flagged as both 'nullable' and 'must be unique':
Anomaly not detected -
Tables that contain a single column:
Anomaly not detected -
Tables with incrementing column names, potentially indicating denormalization:
Anomaly not detected -
Columns whose default value is the word 'NULL' or 'null', but the SQL NULL value may have been intended:
Anomaly not detected