On 12/16/2012 09:13 PM, Richard Hipp wrote: > > > On Sun, Dec 16, 2012 at 1:45 PM, Ron Aaron <r...@ronware.org > <mailto:r...@ronware.org>> wrote: > > Thank you, that worked; but I had custom fields in my ticket > table, which I had to remember to save and then restore after the > change. > > Does this need to be done on every repo I have or only on those > with non-standard ticket tables? It's rather an unfortunate thing > to have to do... > > > It does not have to be done at all for fully custom implementations. > > The new default "Ticket New", "Ticket Edit" and "Ticket View" scripts > require the new TICKETCHNG table. You should only have problems if > you were using a customized table definition but continued to use the > default viewing and editing scripts.
Hmm. In the one case I'm speaking of, the table definition was updated, and so was the view and new but not the edit script. > When you do that and you upgrade Fossil, you'll get the new and > improved viewing and editing scripts that require the TICKETCHNG table > but the older table definitions without the TICKETCHNG table. > > It seems like if you had updated your TICKET table defintion, you > would also have added custom viewing and editing scripts to show the > new fields you added to TICKET, no? Well, in this case, not completely; no 'edit' script was modified. So the problem occurs when you have an incompletely customized fossil setup.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
