On Aug 24, 2008, at 4:37 PM, Remy Blank wrote: > Mr. Meitar Moscovitz wrote: >> Noah, you mentioned: >>> This was exactly how the 0.10 version of the plugin tried to >>> work, just using some funky SQL to pull data from a semi- >>> formatted text field. This didn't work well at all, hence the >>> massive warning against using that iteration of the plugin. >> Do you mean to say that the TracLinks-style ticket-as-keyword is >> something that was tried but "didn't work well at all"? Apologies, >> I'm not following your meaning…maybe I need my coffee worse than I >> thought. > > I don't think so. He's referring to the way the plugin stores the > ticket relations. There were two major revisions of the > MasterTicketsPlugin: the 0.10 version and the 0.11 version. The > former used a custom ticket field with a space-separated list of > ticket numbers as the storage mechanism, and references were > extracted with "funky SQL". The latter uses a DB table as storage, > which allows extracting the references with "traditional SQL", and > only uses the custom field for display.
Oh, I see. I've actually never used the MasterTicketsPlugin and in fact am rather unfamiliar with most of the available plugins. > I'll have to let him comment himself as to why the first approach > was so bad, as I don't know for sure. But in both cases, there is > additional code that manages (and enforces) the dependencies. What I > find appealing with your approach is that it uses convention instead > of enforcement to achieve the same effect, and with #1791, it would > even allow the references to be real links, provided you put the > references into a custom field. > > -- Remy I like that phrase, "convention instead of enforcement." I bet I'll use that again somewhere soon. :) ticket:1791 looks interesting. On a related note, I found the AutoQueryPlugin recently, which looks similar. Do you (or does anyone else) know if this plugin would do what you describe here, i.e., actually linkifying the subticket keywords thanks to their TracLinks convention? http://trac-hacks.org/wiki/AutoQueryPlugin I might have a play with it sometime in the near future to find out if it does. Personally, I think it makes more sense to keep such subticket references in the keywords field instead of a custom field as the whole notion is conceptually a keyword (and nothing more). It's only through an individual project's conventions that the notion of a "subticket" keyword actually makes any sense. For instance, it's conceivable that keywords that begin with an octothorp mean something entirely different to some problem domains. However, for the same reasons, I can also see how others might consider this approach "overloading the keywords field" and would want a custom text field specifically for this use. Cheers, -- -Meitar Moscovitz Personal: http://maymay.net Professional: http://MeitarMoscovitz.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
