On 9/28/15, David Given <d...@cowlark.com> wrote:
> On 28/09/15 21:14, Richard Hipp wrote:
> [...]
>> Perhaps this following change will help. Please try and let us know:
>
> Thanks! Unfortunately:
>
>> - "SELECT strftime('%%s',mtime), objid, coalesce(ecomment,comment),"
>> + "SELECT strftime('%%s',coalesce(emtime,mtime),"
Ugh. OK. I looked at the schema, this time, and it turns out that
the event.mtime field should already reflect the editing time of the
check-in. So if you have fixed the timestamps on *all* of your
check-ins so that they are in chronological order, the export *should*
work. If it does not then I don't have any clues why.
You can use the "fossil test-timewarp-list" command to get a list of
check-ins that are not in chronological order and which need fixing
up.
>
> There's a missing close parenthesis for strftime; this trivially fixed.
> But less easy to change is that there's no emtime field in the event table.
>
> There ought to be a cleverer way to do this than just relying on the
> timestamp (which can be wrong). Isn't there an SQL example which uses a
> recursive query to walk the commit tree? That way we'd be guaranteed to
> get a correct order.
>
> --
> ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
> │ "There is nothing in the world so dangerous --- and I mean *nothing*
> │ --- as a children's story that happens to be true." --- Master Li Kao,
> │ _The Bridge of Birds_
>
>
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
