On Mon, Nov 3, 2014 at 8:13 PM, E. Timothy Uy <[email protected]> wrote:
> I found some posts in the past describing fixing time-warps using tags. How
> does this process get initiated? I found two while trying to export to .git
>
The test_timewarps webpage will show them all to you. Example:
http://www.sqlite.org/src/test_timewarps
In the example above, most of the timewarps have been fixed. To fix them,
simple edit check-ins and change their time.
I intentionally left one timewarp in SQLite unfixed. See the
https://www.sqlite.org/src/timeline?p=3f30f00a384d23&d=3f30f00a384d235
timeline. I left this one as a test case for ensuring that Fossil can
display timewarps correctly.
>
> sqlite> SELECT l.*, ep.mtime, ec.mtime FROM plink l LEFT JOIN event ep ON
> pid = ep.objid LEFT JOIN event ec ON cid = ec.objid WHERE ep.mtime >
> ec.mtime LIMIT 10;
>
> 35460|35462|1|2455469.26833333|2455469.46484954|2455469.26833333
>
> 35450|35453|1|2455468.35189815|2455468.80332176|2455468.35189815
>
> Respectfully,
>
> Tim
> _______________________________________________
> sqlite-users mailing list
> [email protected]
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
--
D. Richard Hipp
[email protected]
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
