On Fri, Sep 14, 2012 at 3:09 PM, Christopher Nelson
<chris.nelson.1...@gmail.com> wrote:
> On Fri, Sep 14, 2012 at 2:16 PM, Steffen Hoffmann <hoff...@web.de> wrote:
> > On 14.09.2012 15:19, Christopher Nelson wrote:
> > Doing automatic ticket changes for your PM stuff will not work well, if
> > at all. Doing regular ticket changes each re-scheduling would leave a
> > changes entry and change comment for each action to each ticket, and
> > your tickets history will quickly grow beyond usable limits.
>
> A valid point (and one already raised by a co-worker) but I'm still
> experimenting. If that's true, a listener that does:
>
> * recompute schedule
> * update tickets
>
> can easily morph to:
>
> * recompute schedule
> * update another table
>
> > I conclude, that you'll likely need to
> > * mess directly with PM-related ticket field values and spare the
> > planning history
> > * do it in a dedicated table outside of Trac db tables 'ticket' and
> > 'ticket_custom' (preferred).
>
> I think that the history is important and I'm not averse to an custom
> table.
> ...
So, I have a working prototype but I'm struggling with the names of my
tables. Judging from MasterTickets and Subtickets plugins, there
doesn't seem to be common idiom or convention for naming tables to
avoid name conflicts with other plugins.
My tables will reside in the Trac database (environment) so "schedule"
seems a bad name, something someone else (or a future revision to
Trac) might want to use. I doubt there's an RDBMS-agnostic namespace
mechanism so I'm left with some plugin-specific prefix like
"pm_schedule" or "TracPM-schedule" or something. Can someone think of
a plugin that tries to be friendlier to other plugins so I can copy
its technique and start a trend?
Chris
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to trac-dev@googlegroups.com.
To unsubscribe from this group, send email to
trac-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
