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.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
