On Wed, Nov 26, 2014 at 7:33 PM, Baruch Burstein <bmburst...@gmail.com> wrote:
> P.S. If changing the schema is indeed a big deal that you would rather > avoid as much as possible, and if you do decide to go ahead and change it > now, maybe you can have a look at this bug ( > http://fossil-scm.org/index.html/tktview?name=d26a9d9e2b) too. I am not > sure how to fix it myself, but I think that fixing it may require a schema > change, and if so you might as well do all the changes in one release. > Now that you mention it... i also have a small schema wish: i want the full list of files for a given checkin. i've banged my head over SQL-only solutions, and don't see how to get it without parsing the manifest. It would be easy to add during crosslinking, but there's currently no place for it (and i'm not quite certain where it would fit best). My point was really only to float the idea of doing a "schema change sprint," where we bundle such changes up for a "rebuild release." -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-dev mailing list fossil-dev@lists.fossil-scm.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/fossil-dev
