You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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 betracker/src/Application/Model/Ticket.php
Lines 354 to 360 in b9fd435
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
).The text was updated successfully, but these errors were encountered: