On Tue, Aug 6, 2013 at 5:27 PM, Eric Rubin-Smith <[email protected]> wrote:
> > ... i.e. silently ignore capitalized POST argument names. Is there a >>> reason for that? >>> >> >> Yes there is. >> >> > Thanks Richard. So I was initially planning on doing a brute-force > migration to the new ticket table schema with the lowercase letters. But > it sounds like that is a pointless exercise, since the real point of truth > is the artifacts (and I should have known that, since I read all your > start-up docs). > > So I guess I have two options: > > * Blow out all the artifacts into a directory, munge them to have the new > column names, and then rebuild the database from the munged artifacts. > * Generate new artifacts indicating additions of tags that are the new > column names. Leave the old tags alone, and just adjust the ticket view > and edit pages' code. > > I assume you will find the former distasteful and will recommend the > latter. Any easy way to accomplish that, or should I start hacking up a > script? > I have no recommendation one way or the other. Use whichever approach seems to work best for you. There are no tools in Fossil that I recall that will help with this. I think you need a script. -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
