Content
View differences
Updated by Kabiru Mwenja about 2 months ago
Follow-up of ##73334 <mention class="mention" data-id="73334" data-type="work_package" data-text="#73334">#73334</mention>
When the web app or the mobile app renders work packages it needs to decide (based on the setting) which ID to render for work packages. Either the database ID in the "classic" mode or the semantic ID in the project-based work package ID mode.
<br>
**Option A) Add a method in WorkPackage which returns the value based on the setting) (= "decide on the fly")**
\+ easy to implement
\+ nothing needs to be saved to the database and kept in sync when switching the setting
\- maybe a little bit slower, since the setting needs to be queried for (almost) each request which involves a work package
<br>
**Option B) Use a separate column** `**user_facing_identifier**` **(name is WIP, better suggestions are welcome) (= "decide upfront")**
\+ faster on read
\- needs to be set on write (e.g. in the migration job and each time the semantic identifier changes)
\- when switching from "project-based work package IDs" to "database based IDs" we need a migration job to change this column
When the web app or the mobile app renders work packages it needs to decide (based on the setting) which ID to render for work packages. Either the database ID in the "classic" mode or the semantic ID in the project-based work package ID mode.
<br>
**Option A) Add a method in WorkPackage which returns the value based on the setting) (= "decide on the fly")**
\+ easy to implement
\+ nothing needs to be saved to the database and kept in sync when switching the setting
\- maybe a little bit slower, since the setting needs to be queried for (almost) each request which involves a work package
<br>
**Option B) Use a separate column** `**user_facing_identifier**` **(name is WIP, better suggestions are welcome) (= "decide upfront")**
\+ faster on read
\- needs to be set on write (e.g. in the migration job and each time the semantic identifier changes)
\- when switching from "project-based work package IDs" to "database based IDs" we need a migration job to change this column