SchemaSpy Analysis of topp.wc - 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
  all	106,520
  argos	31,363
  argos_diag_history	24,961
  bar	24,586
  behavior	9,977
  columns	20
  corrupt	20,475
  deployment	40
  dtag_metadata	1
  fastgps	19,680
  haulout	616
  histos	2,610
  justin_2017_metadata	11
  justin_metadata	11
  labels	105
  locations	41,203
  metadata	58
  minmaxdepth	2,756
  patrick_metadata	5
  prev_argos_metadata	14
  previous_metadata	0
  rawargos	106,680
  rtc	77
  series	177
  seriesrange	4
  sst	1,040
  status	2,669
  summary	40
  uga_metadata	1

  29 instances of anomaly detected

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

• Tables that contain a single column:
  Anomaly not detected

• Tables with incrementing column names, potentially indicating denormalization:

  Table
  all
  argos
  behavior
  corrupt
  fastgps
  histos
  rawargos

  7 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