You have to run
fossil rebuild
on _all_ repositories with the new definition.
This rebuilds the derived tables (TICKET, TICKETCHNG) from the actual
tickets, and ensures that they actually have the new column you
defined.
On Tue, Sep 2, 2014 at 11:36 AM, Eric Rubin-Smith eas@gmail.com wrote:
In one of my fossil repos, I edited the tickets table by adding a column.
I wanted to pull the new column definition into a repo clone, so I said
fossil config pull all
from the other repo, to no avail. New reports, the New Ticket and Edit
Ticket pages and so on were properly synchronized, but the table definition
itself was not.
This leads to this error message in one of the reports I have defined that
uses the new column:
SQLITE_ERROR: no such column: releaseGate
Other commands that did not work:
fossil config pull ticket
fossil config pull ticket --overwrite
fossil pull
I have seen this every time I have tried to add a column to the tickets
table. I normally work around it by copy-pasting the ticket definitions,
but that is probably not going to be acceptable for my other users.
Am I doing something wrong?
Eric
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Andreas Kupries
Senior Tcl Developer
Code to Cloud: Smarter, Safer, Faster™
F: 778.786.1133
andre...@activestate.com, http://www.activestate.com
Learn about Stackato for Private PaaS: http://www.activestate.com/stackato
21'st Tcl/Tk Conference: Nov 10-14, Portland, OR, USA --
http://www.tcl.tk/community/tcl2014/
Send mail to tclconfere...@googlegroups.com, by Sep 8
Registration is open.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
