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.
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
signature.asc
Description: OpenPGP digital signature
