SchemaSpy Analysis of tariqa3 - 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
  briefcase_content_backup.content_id	briefcase_content.content_id
  briefcase_content_backup.folder_id	briefcase_folders.folder_id
  briefcase_content_backup.type_id	briefcase_contents_types.type_id
  briefcase_content_backup.user_id	known_users.user_id
  briefcase_folders.user_id	known_users.user_id
  rss_log.log_id	app_log.log_id
  rss_log.user_id	known_users.user_id

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

  Table	Column
  app_log_individualusersperday	user_id
  app_log_pageslist	page
  app_log_userslist	user_id

  3 instances of anomaly detected

• Tables with incrementing column names, potentially indicating denormalization:

  Table
  languages

  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