Changes between Version 3 and Version 4 of RelationalDesign


Ignore:
Timestamp:
09/02/26 15:52:17 (4 days ago)
Author:
236024
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • RelationalDesign

    v3 v4  
    11= Relational Design =
    22
    3 This page documents the relational design for BEST Skopje Hub, based on !ERModel_v10. The design uses partial transformation from the ER model into a PostgreSQL relational schema. Strong entities are mapped directly to relations, weak entities include the primary keys of their owner entities, specializations are mapped with one relation for the supertype and one relation for each subtype, and M:N relationships are mapped as separate relations.
     3This page documents the relational design for BEST Skopje Hub, based on ERModel_v10. The design uses partial transformation from the ER model into a PostgreSQL relational schema. Strong entities are mapped directly to relations, weak entities include the primary keys of their owner entities, specializations are mapped with one relation for the supertype and one relation for each subtype, and M:N relationships are mapped as separate relations.
    44
    55== Descriptive representation of the relational schema ==
    … …  
    202202The specialization of students into members and then into observers, young members, full members, and alumni is represented through subtype tables whose primary keys are also foreign keys. `young_members` also contains `mentor_index`, which represents the mentorship relationship directly as a foreign key to `full_members`.
    203203
    204 The weak entities from !ERModel_v10 are represented with composite primary keys where they still depend on an owner entity. `event_functions` uses `(ee_id, ef_no)`, and `event_sessions` uses `(ee_id, es_no)`. Other concrete entities such as `activity_sessions` and `event_editions` use their own numeric identifiers.
     204The weak entities from ERModel_v10 are represented with composite primary keys where they still depend on an owner entity. `event_functions` uses `(ee_id, ef_no)`, and `event_sessions` uses `(ee_id, es_no)`. Other concrete entities such as `activity_sessions` and `event_editions` use their own numeric identifiers.
    205205
    206206The Locations entity is represented with `locations`. The relationship between !EventEditions and Locations is represented with `event_edition_locations`.
    … …  
    228228== AI Use ==
    229229
    230 AI was used during this phase as a consultation, drafting, and checking tool while preparing the relational design from the already completed !ERModel_v10. The AI-assisted parts were reviewed against the existing ER model and project requirements before being included.
     230AI was used during this phase as a consultation, drafting, and checking tool while preparing the relational design from the already completed ERModel_v10. The AI-assisted parts were reviewed against the existing ER model and project requirements before being included.
    231231
    232232Full AI usage documentation: [wiki:RelationalDesignAIUsage RelationalDesignAIUsage].