Thank you, that is helpful information. On Tue, Nov 4, 2014 at 11:52 PM, Stephan Beal <sgb...@googlemail.com> wrote:
> On Wed, Nov 5, 2014 at 7:07 AM, E. Timothy Uy <t...@loqu8.com> wrote: > > > The problem is ultimately not time-warps. DRH can confirm - the problem > is > > actually inside fossil and sqlite.fossil. Very early on in sqlite.fossil > > there are entries in the plink table where the parent id (pid) is greater > > than the commit id (cid). There are over a thousand of these. > > > Those IDs are _transient_, not part of the historical record. The "child ID > comes before parent ID" behaviour also appears on completely benign repos > (i've seen it before in my own while testing libfossil). > > > > > If I had more brain cells, I could perhaps invent a way to efficiently > use > > the plink table to generate the proper export list where parents always > > come before children regardless of mtime. > > > > i've also attempted something similar in libfossil, but haven't been > successful. The RIDs cannot be used to figure it out, and neither can > mtime. The only 100% reliable way i know of traversing the history is to > read each manifest, as the P-cards give us that piece of context we need to > know the ordering. > > -- > ----- 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 > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users