Skip to content

Table: damage_people

Description (EN): This table represents damages reported to people. In the database's inheritance architecture, it acts as a direct sub-type of the damage table. It does not store redundant descriptive columns; instead, it uses a shared primary key to inherit all high-level attributes (such as name, location, management type, and geometry) from its parent damage record.

Column Structure

Column Data type Definition Example value Constraint? Geometry? Comments
id BIGINT Unique identifier for damages to people 42 PK, FK No Primary key that also acts as a Foreign Key referencing damage.id
number_of_dead INTEGER [...] [...] - No -
number_of_injured INTEGER [...] [...] - No -
number_of_missing INTEGER [...] [...] - No -

Relationships

  • Inherits from (Sub-type of): damage. The damage_people table is a specialized extension of the damage table.
  • Affects: component (One or more damages affect a component or its subclasses)
  • Is reported by: survey (One or more damages is reported in a survey)
  • Reported in: attachment (A damage is reported in one or more attachments)
  • Results in: economic_loss

!!! tip "Where is the rest of the data?" To find the name, geographical location (geometry, town, country), or other details of a damage to people, you must join this table with the damage record that shares the exact same id.

Example Query

Retrieve a list of all damages to people, including their descriptions, towns, and spatial coordinates, by joining the table with its parent damage entity:

SELECT
    dp.*,
    d.*
FROM 
    damage_people dp  join damage d on dp.id = d.id