Changes between Version 1 and Version 2 of RelationalDesign

Timestamp:

08/29/26 13:22:39 (8 days ago)

Author:

236024

Comment:

--

RelationalDesign

@@ -186 +186 @@
 }}}
 
+In the physical PostgreSQL schema, `application_id` is implemented as an automatically generated identity value. It is still listed as the primary key of `applications`, but it does not have to be manually inserted in the data loading script.
+
+The `applications` relation is used only when there is an actual application process. Public attendance for events such as Job Fair, and open registration-style attendance for events such as beBESTie, is not represented as an application in this phase. For Hackathon and BEST Course in Summer participation applications, the `motivational_letter` attribute represents the most important motivation/answer kept from an external application form.
+
 The 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`.
 
@@ -208 +212 @@
 == Relational diagram ==
 
-The relational diagram will be exported from DBeaver after running `schema_creation.sql` in the assigned PostgreSQL database and opening the `project` schema diagram. The diagram will use crow-feet notation and be exported as `relational_schema.jpg`.
+The relational diagram was exported from DBeaver after running `schema_creation.sql` in the assigned PostgreSQL database and opening the `project` schema diagram. The diagram uses crow-feet notation.
+
+[[Image(relational_schema.png, width=100%)]]
 
 == AI Use ==