SchemaSpy Analysis of frontend.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
  execution_audit
  user_registration_message

  2 instances of anomaly detected

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

  Column
  annex.name
  applicant.id_form
  city.name
  commune.name
  district.name
  financial_installment.id_form
  folder.id_user
  folder.name
  intervention_category.name
  intervention_category.number
  legal_base.name
  operation.name
  operation.number
  prerequisite_of_public_assistance.id_public_assistance
  priority_axis.name
  priority_axis.number
  project.id_form
  project_description.id_form
  province.name
  public_assistance.id_project
  ranking_list.name
  sec_operator.login
  sec_permission.name
  sec_role.registration_date
  sec_system.registration_date
  statement.content
  suboperation.name
  type_of_applicant.name
  type_of_project.name
  type_of_record.name

  30 instances of anomaly 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