| SchemaSpy Analysis of alter.public - Anomalies | Generated by SchemaSpy |
| Things that might not be 'quite right' about your schema: | Please support this project |
-
Columns whose name and type imply a relationship to another table's primary key:
12 instances of anomaly detectedChild Column Implied Parent Column mis_banks.iso countries.iso mis_bids.project_id mis_projects.project_id mis_customer_payments.payment_id mis_payments.payment_id mis_customers_products_map.map_id mis_vendors_products_map.map_id mis_delivery_notes.sale_invoice_id mis_sale_invoices.sale_invoice_id mis_monitoring.user_id mis_user_preferences.user_id mis_packages.package_key apm_package_types.package_key mis_plants_t.plant_id mis_plants.plant_id mis_print.user_id mis_user_preferences.user_id mis_sale_paydates.date_id mis_customer_dates.date_id mis_user_preferences.plant_id mis_plants.plant_id mis_user_preferences.store_id mis_stores.store_id -
Tables without indexes:
2 instances of anomaly detectedTable Rows mis_plants_t 3 mis_print 0 -
Columns that are flagged as both 'nullable' and 'must be unique':
23 instances of anomaly detectedColumn acs_object_types.table_name apm_package_types.pretty_plural auth_authorities.short_name mis_accounts.account_code mis_acct_iva.acct_iva_month mis_acct_iva.acct_iva_year mis_acct_plan_types.acct_plan_type_code mis_counters.counter_section mis_counters.counter_type mis_customers_products_map.customer_id mis_customers_products_map.customer_id mis_customers_products_map.product_code mis_customers_products_map.product_id mis_iva_ctr.acct_iva_month mis_iva_ctr.acct_iva_year mis_iva_ctr.counter_id mis_parties.party_code mis_product_categories.product_category_code mis_products.product_code mis_um.um_code mis_wh_mov_types.wh_mov_type_code parties.email users.screen_name -
Tables that contain a single column:
1 instance of anomaly detectedTable Column mis_packages package_key - Tables with incrementing column names, potentially indicating denormalization:
-
Columns whose default value is the word 'NULL' or 'null', but the SQL NULL value may have been intended:
Anomaly not detected