SchemaSpy Analysis of srdb.srdb - 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
  bioparams.assessid	assessment.assessid
  mostrecent.assessid	assessment.assessid
  mostrecent.stockid	stock.stockid
  reference_point_units_view.assessid	assessment.assessid
  reference_point_values_view.assessid	assessment.assessid
  timeseries_units_view.assessid	assessment.assessid
  timeseries_values_view.assessid	assessment.assessid
  tsrelative_explicit_view.assessid	assessment.assessid

  8 instances of anomaly detected

• Tables without indexes:

  Table	Rows
  bioparams	4,676
  fishbasesaupcodes	279
  lmetostocks	456
  mostrecent	360
  reference_point_units_view	333
  reference_point_values_view	333
  referencedoc	3,693
  risfieldvalues	12
  timeseries_units_view	355
  timeseries_values_view	16,308
  tsrelative_explicit_view	28,977

  11 instances of anomaly detected

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

  Column
  taxonomy.scientificname

  1 instance of anomaly detected

• Tables that contain a single column:
  Anomaly not detected

• Tables with incrementing column names, potentially indicating denormalization:

  Table
  taxonomy

  1 instance 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