> On Mon, Sep 17, 2012 at 11:12 AM, Ethan Jucovy <[email protected]> > wrote: > ... > Or, if you *do* feel like just adding a dependency on TracSqlHelperScript, > like I ended up doing, you could basically just copy all of the setup code > in MultiRepoSearchPlugin here[1] and adjusting it for your needs. In > addition to demonstrating schema definition and table creation, it also uses > Trac's system table to track what upgrades need to occur, and a neat little > upgrade-steps-based-on-current-version framework thingie that I copied from > TracHours. (That's the `version()` and `steps =` stuff.) I *think* this is > considered The Right Way to manage upgrades in Trac plugins these days.
Thanks. I found an example in Subtickets plugin and will look at TracHours, too. -- You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en.
