Hello Richard and all.
1. I assume it affects only import/export with options "--import-marks/--export-marks"... 2. Therefore I think, that the export of Andreas was never affected by this mistake, because he does whole (not partial) export (so without marks). 3. I cannot confirm the mentioned commit of Jan changes something (if options "--import-marks/--export-marks" used). In contrary I'm sure it still does not work, because I made my latest test-export on 02 May 2018, where Jan's commit was already pushed to tcl-repo (and the export still failed). 4. The idea to change order by clause (e. g. sort by rowid and not by date) sounds plausible (and I believe ordering by any date is wrong, at least by the usage of option "--git"). Regards, Sergey. 03.05.2018 19:55, Richard Hipp wrote: > Fossil does its export in timestamp order. (Key source line here: > https://www.fossil-scm.org/fossil/artifact/20d1516bc?ln=611 [1]) But Jan > did a check-in with a bad timestamp. (See > https://core.tcl.tk/tcl/timeline?unhide=on&n=25&y=ci&c=567e61b329c6b6f7872f > [2]) > That caused the MARKs to occur out-of-order. Jan subsequently fixed > the timestamp on the check-in (see > https://core.tcl.tk/tcl/info/a0ad546f77dfc5a2 [3]) so the export should be > working now. > > Andreas - please confirm that the export has been working ever since > Jan fixed the timestamp on 2018-04-25. > > I suppose a proper fix would be to change the ORDER BY clause to cause > the check-ins to be scanned in a dependency order, rather than in > chronological order. I'm not sure exactly what that SQL would be, > though.... Links: ------ [1] https://www.fossil-scm.org/fossil/artifact/20d1516bc?ln=611 [2] https://core.tcl.tk/tcl/timeline?unhide=on&n=25&y=ci&c=567e61b329c6b6f7872f [3] https://core.tcl.tk/tcl/info/a0ad546f77dfc5a2 _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
