On Sat, May 21, 2016 at 4:36 PM, Steve Schow <st...@bstage.com> wrote:
> Thanks for that information. I was not aware that ticket changes involved > artifacts also. > Everything in Fossil is stored in artifacts. The DB serves as artifact storage, indexing of artifacts and a convenient cache of data from the artifacts. All the artifacts could be dumped into files, then later, a new DB could be constructed from the artifacts. > A few months back when I first started using fossil I batch changed a > bunch of tickets using SQL, I changed the value of the subsystem column.. > since then I’ve gone in and edited many of the same tickets using the web > ui and the subsystem value didn’t seem to revert back to anything, and > everything seems fine, but now you have me a little worried that in some > cases the artifacts of those tickets will be somehow out of sync with the > SQL at some point in the future. > As long as your repository is not exchanging ticket updates with another, the DB tables should retain all the information. > But thanks for the heads up, in the future if I am going to batch update > a bunch of tickets I will use the fossil ticket command to do it in some > way. > That would be much safer.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
