Changes between Version 8 and Version 9 of ERModel


Ignore:
Timestamp:
08/23/26 15:59:23 (3 weeks ago)
Author:
213257
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ERModel

    v8 v9  
    114114 * status (VARCHAR(32), required) - Current state of the inquiry. Allowed values: "New", "Replied", "Closed". Default: "New".
    115115 * created_at (TIMESTAMP, required) - Automatically set to current timestamp when inquiry is submitted. Used for sorting.
     116 * response (TEXT, optional) - The agent reply text to the client inquiry. After being filled in the status of the inquiry changes to "Replied".
     117 * responded_at (TIMESTAMP, optional) - Timestamp of when the agent submitted the response.
     118
    116119
    117120**Appointment**
     
    147150 * Participation: Partial on both sides.
    148151
    149 * Has (Building-Floor)
    150  * The Has relationship represents floors contained within buildings. Each floor belongs to exactly one building, while buildings contain multiple floors.
     152* Contains (Building-Floor)
     153 * The Contains relationship represents floors contained within buildings. Each floor belongs to exactly one building, while buildings contain multiple floors.
    151154 * Cardinality: One-to-Many (1:N)
    152155 * Participation: Total on Floor side because every floor needs a building, partial on Building side buildings under construction may lack final floor definitions.
    153156
    154 * Has (Unit-Floor)
    155  * The Has relationship represents units contained within floors. Each unit is on exactly one floor (in most real world scenarios the unit can span multiple floors but it has a door on one floor only), while floors contain multiple units.
     157* LocatedOn (Unit-Floor)
     158 * The LocatedOn relationship represents units contained within floors. Each unit is on exactly one floor (in most real world scenarios the unit can span multiple floors but it has a door on one floor only), while floors contain multiple units.
    156159 * Cardinality: One-to-Many (1:N)
    157160 * Participation: Total on Unit side (every unit needs a floor), partial on Floor side (may lack unit definition in early stages of construction).
    158161
    159 * Manages (Admin-Building)
    160  * The Manages relationship indicates which admin created and manages a building. Each building has one managing admin for clear accountability, while admins manage multiple buildings. Necessary for access control.
     162* ManagesBuilding (Admin-Building)
     163 * The ManagesBuilding relationship indicates which admin created and manages a building. Each building has one managing admin for clear accountability, while admins manage multiple buildings. Necessary for access control.
    161164 * Cardinality: One-to-Many (1:N)
    162165 * Participation: Total on Building side, partial on Admin side.
    163166
    164 * Manages (Admin-Floor)
    165  * The Manages relationship indicates which admin created and manages a floor. Each floor has one managing admin responsible for floor details and layout images, while admins manage multiple floors.
     167* ManagesFloor (Admin-Floor)
     168 * The ManagesFloor relationship indicates which admin created and manages a floor. Each floor has one managing admin responsible for floor details and layout images, while admins manage multiple floors.
    166169 * Cardinality: One-to-Many (1:N)
    167170 * Participation: Total on Floor side, partial on Admin side.
    168171
    169 * Manages (Admin-Unit)
    170  * The Manages relationship indicates which admin created and manages a unit. Each unit has one managing admin for accountability on pricing and availability, while admins manage multiple units.
     172* ManagesUnit (Admin-Unit)
     173 * The ManagesUnit relationship indicates which admin created and manages a unit. Each unit has one managing admin for accountability on pricing and availability, while admins manage multiple units.
    171174 * Cardinality: One-to-Many (1:N)
    172175 * Participation: Total on Unit side, partial on Admin side.
     
    219222 * Added relation between admin and floor
    220223 * full_name on architect entity changed from multivalue attribute to an attribute
     224* Version 03
     225 * Expanded Inquiry to include response and responded_at attributes.
     226 * Renamed "Has" relationships to unique names Contains (Building-Floor), LocatedOn (Floor-Unit).
     227 * Renamed "Manages" relationships to unique names ManagesBuilding, ManagesFloor, ManagesUnit.
     228
     229