>> On Mon, Sep 17, 2012 at 11:12 AM, Ethan Jucovy <ethan.juc...@gmail.com> >> 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.
Any advice on how to add fields to a private table in an upgrade script? -- A: Top-posting. Q: What is the most annoying thing in e-mail? -- 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.
