SchemaSpy Analysis of sola.administrative - AnomaliesThe SOLA implementation of the LADM Administrative package. Models land use rights and restrictions how those rights and restrictions relate to property and people.

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
  Function: ba_unit_name_is_valid
  Function: get_ba_unit_pending_action
  Function: get_calculated_area_size_action
  Function: get_concatenated_name
  Function: get_objections
  Function: get_parcel_ownernames
  Function: getsysregmanagement
  Function: getsysregprogress
  Function: getsysregstatus
  Sequence: ba_unit_first_name_part_seq
  Sequence: ba_unit_last_name_part_seq
  Sequence: notation_reference_nr_seq
  Sequence: rrr_nr_seq
  Trigger Function: f_for_tbl_rrr_trg_change_from_pending

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