SchemaSpy Analysis of osm.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
  geometry_columns.srid	spatial_ref_sys.srid
  planet_osm_nodes.id	planet_osm_rels.id
  planet_osm_ways.id	planet_osm_rels.id

  3 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:
  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