While moving code like this it may also be a good idea to add computed columns for ticket properties depending on the encoding profile. The encoding profile of a ticket and the properties of a ticket (e.g. if depends on other tickets) rarely change but lot's of joins are required to fetch related properties.
We should also define a convention for computed columns (like _is_master).
A while ago we already planed to move some commonly (in the tracker) used properties to columns in
tbl_ticket. A first guidance would probably behttps://github.com/crs-tools/tracker/blob/b9fd43588ab0f06b40b22791af54324aa0cc1f3e/src/Application/Model/Ticket.php#L354-L360
While moving code like this it may also be a good idea to add computed columns for ticket properties depending on the encoding profile. The encoding profile of a ticket and the properties of a ticket (e.g. if depends on other tickets) rarely change but lot's of joins are required to fetch related properties.
We should also define a convention for computed columns (like
_is_master).