On Wed, Sep 19, 2012 at 9:38 PM, Christopher Nelson <chris.nelson.1...@gmail.com> wrote: > On Fri, Sep 14, 2012 at 3:09 PM, Christopher Nelson > <chris.nelson.1...@gmail.com> wrote: >... >> 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?
Still looking for table naming advice but I'm now keeping schedule history in a second private table and I can reschedule 4k tickets in 25 seconds. In most cases, pruning to active tickets will make it much, much faster so I think I'm good. -- 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.
