SchemaSpy Analysis of transmart.searchapp - Anomalies | 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 plugin_module_backup.module_seq plugin_module.module_seq plugin_module_backup.plugin_seq plugin.plugin_seq search_app_access_log.id search_gene_signature_item.id search_auth_principal.id search_gene_signature_item.id search_custom_filter_item.search_custom_filter_id search_custom_filter.search_custom_filter_id search_gene_signature_item.search_gene_signature_id search_gene_signature.search_gene_signature_id search_request_map.id search_gene_signature_item.id search_role.id search_gene_signature_item.id search_secure_object_path.search_secure_object_id search_secure_object.search_secure_object_id search_user_settings.id search_gene_signature_item.id -
Tables without indexes:
Table Rows plugin_module_backup 0 report 0 report_item 0 search_app_access_log 0 search_auth_group_member 0 search_bio_mkr_correl_fast_mv 0 search_request_map 17 search_role_auth_user 8 subset 0 -
Columns that are flagged as both 'nullable' and 'must be unique':
Column search_auth_user.federated_id -
Tables that contain a single column:
Anomaly not detected -
Tables with incrementing column names, potentially indicating denormalization:
Table search_gene_signature search_taxonomy_lineage subset -
Columns whose default value is the word 'NULL' or 'null', but the SQL NULL value may have been intended:
Anomaly not detected