On Thu, Jan 15, 2015 at 3:56 PM, Ron W <[email protected]> wrote: > On Thu, Jan 15, 2015 at 4:14 PM, Rich Neswold <[email protected]> > wrote: > >> Maybe the fossil schema can be enhanced by adding triggers that prevent >> UPDATEs from occurring on critical columns. >> > > Not sure how much value that would add because all the actual (repository) > data is in the blobs. The ID of each blob is its hash. The database tables > can be reconstructed from the blobs (except for the ones containing the > local configuration information). > > Basically it would be weighing the risk of messing the meta data vs the > overhead of the triggers. From what I've read, rebuilding a Fossil database > is a very, very rare event. >
When I look at the schema of a fossil repo, I see comments like: -- Do not change any column that begins with tkt_ Maybe I misunderstood the meaning. I took it to mean don't change the values of these fields. But maybe it means don't change the column's type or name so queries don't break.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
