| 21 | No. As with `ticket_change` this will be only for the change records. It makes a great deal of flexibility to keep these information separately, only joining tables on demand. While it might be technically possible to get the same information from `tag_change` by examining tag history of a given resource, this would be far more expensive. Building a view would be another option, but for one this is not easy to do in a generic way (independent of db-backend's SQL flavor), and the Trac db schema is not highly normalized anyway. |