SchemaSpy Analysis of webco_3.5.5.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
  bibliographic_record_configuration	0
  bibliographic_record_ext	0
  bibliographic_record_helix_ext	0
  holding_ext	0
  import_session	0
  notification_channel	0
  person_ext	0
  pir_item	0
  planq_version	0
  resource_child	0
  resource_container_tcm	0
  resource_ext	0
  resource_parent	0
  resource_type_ext	0
  task_parent_tcm	0
  wco_version	1

  16 instances of anomaly detected

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

  Column
  allocation_item.resource_schedule_oid
  freelancer_person_location.location_oid
  freelancer_person_location.person_oid
  person.userid
  person.userid
  pir_person_location.location_oid
  pir_person_location.person_oid
  resource.foreignid
  resource_controller.device_id
  task_group.group_oid
  task_group.task_oid
  task_person.person_oid
  task_person.task_oid
  task_resource.resource_oid
  task_resource.task_oid
  task_resource_type.rtype_oid
  task_resource_type.task_oid
  wco_authorization.organization
  wco_authorization.person

  19 instances of anomaly detected

• Tables that contain a single column:

  Table	Column
  import_session	obj_oid
  planq_version	version
  resource_sleep_queue	obj_oid
  resource_wake_queue	obj_oid
  wco_version	version

  5 instances of anomaly detected

• Tables with incrementing column names, potentially indicating denormalization:

  Table
  department
  organization
  person
  person_ext
  pq_organization
  wco_group

  6 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