SchemaSpy Analysis of fossology.public - 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
  jobdepends	147

  1 instance of anomaly detected

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

  Column
  agent_wc.pfile_fk
  licgroup.licgroup_name
  licterm.licterm_name
  licterm_map.licterm_fk
  licterm_map.licterm_words_fk
  licterm_maplic.lic_fk
  licterm_maplic.licterm_fk
  licterm_name.agent_lic_meta_fk
  licterm_name.licterm_fk
  licterm_words.licterm_words_text

  10 instances of anomaly 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