- Tables
- Relationships
- Utility Tables
- Constraints
- Anomalies
- Columns
- Donate

SchemaSpy Analysis of swadroid_db_crypt - 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
  --- | ---
  android_metadata | 0
  courses | 0
  group_course | 0
  group_grouptypes | 0
  group_types | 0
  groups | 0
  notifications | 0
  practice_sessions | 0
  rollcall | 0
  tst_answers | 0
  tst_config | 0
  tst_question_answers | 0
  tst_question_tags | 0
  tst_questions | 0
  tst_questions_course | 0
  tst_tags | 0
  users | 0
  users_courses | 0

  18 instances of anomaly detected

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

- Tables that contain a single column:

  Table | Column
  --- | ---
  android_metadata | locale

  1 instance of anomaly detected

- Tables with incrementing column names, potentially indicating denormalization:

  Table
  notifications
  users

  2 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