SchemaSpy Analysis of openpetra_trunk.public - AnomaliesOpenPetra Version 3 Database

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:
  Anomaly not detected

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

  Column
  a_ep_match.a_detail_i
  a_ep_match.a_detail_i
  a_ep_match.a_match_text_c
  a_ep_match.a_match_text_c
  a_ledger.p_partner_key_n
  m_extract_master.m_extract_name_c
  m_extract_master.m_extract_name_c
  p_person.p_family_id_i
  p_person.p_family_id_i
  p_person.p_family_key_n
  p_person.p_family_key_n
  p_venue.p_venue_code_c
  p_venue.p_venue_code_c
  pt_office_specific_data_labels.pt_off_specific_label1_c
  pt_personal_data_labels.pt_pers_data_label1_c

  15 instances of anomaly detected

• Tables that contain a single column:
  Anomaly not detected

• Tables with incrementing column names, potentially indicating denormalization:

  Table
  pm_pers_office_specific_data
  s_language_specific

  2 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