SchemaSpy Analysis of d47civi_0z3xa - 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:
  Anomaly not detected

• Tables without indexes:

  Table	Rows
  civicrm_install_canary	0

  1 instance of anomaly detected

• Columns that are flagged as both 'nullable' and 'must be unique':

  Column
  civicrm_batch.name
  civicrm_campaign.external_identifier
  civicrm_contact.external_identifier
  civicrm_contact_type.name
  civicrm_contribution.invoice_id
  civicrm_contribution.trxn_id
  civicrm_contribution_recur.invoice_id
  civicrm_contribution_recur.trxn_id
  civicrm_country.iso_code
  civicrm_country.name
  civicrm_custom_group.extends
  civicrm_custom_group.name
  civicrm_cxn.app_guid
  civicrm_cxn.cxn_guid
  civicrm_dedupe_exception.contact_id1
  civicrm_dedupe_exception.contact_id2
  civicrm_domain.name
  civicrm_group.name
  civicrm_group.title
  civicrm_location_type.name
  civicrm_openid.openid
  civicrm_payment_processor_type.name
  civicrm_relationship_type.name_a_b
  civicrm_relationship_type.name_b_a
  civicrm_uf_group.name
  civicrm_word_replacement.domain_id
  civicrm_word_replacement.find_word

  27 instances of anomaly detected

• Tables that contain a single column:

  Table	Column
  civicrm_install_canary	id

  1 instance of anomaly detected

• Tables with incrementing column names, potentially indicating denormalization:

  Table
  civicrm_address
  civicrm_dedupe_exception
  civicrm_prevnext_cache

  3 instances of anomaly detected

• Columns whose default value is the word 'NULL' or 'null', but the SQL NULL value may have been intended:
  Anomaly not detected