SchemaSpy Analysis of postgres.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:

  Child Column	Implied Parent Column
  payment_p2007_01.payment_id	payment.payment_id
  payment_p2007_02.payment_id	payment.payment_id
  payment_p2007_03.payment_id	payment.payment_id
  payment_p2007_04.payment_id	payment.payment_id
  payment_p2007_05.payment_id	payment.payment_id
  payment_p2007_06.payment_id	payment.payment_id

  6 instances of anomaly detected

• Tables without indexes:
  Anomaly not 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
  address

  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