Changes between Initial Version and Version 1 of Ticket #2429, comment 9


Ignore:
Timestamp:
Oct 27, 2013 8:23:31 AM (10 months ago)
Author:
hasienda
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2429, comment 9

    initial v1  
    1919> yep, i think this makes sense.  if this was implemented, could we drop the `tags` table after an upgrade? 
    2020 
    21 No. As with `ticket_change` this will be only for the change records. It make a great deal of flexibility to keep these information separate and only join tables on demand. 
     21No. 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.