> On 12/12/17, J Knight <[email protected]> wrote:
> > Hello. I have some older fossil archives that report:
> >
> > SQLITE_ERROR: table config has no column named mtime
> > fossil: table config has no column named mtime: {REPLACE INTO
> > config(name,value,mtime) VALUES('hash-policy',1,now())}
> >
> > issuing a ârebuildâ and a ârebuild âforceâ gives the same error.
> > Is there
> > some way to bring these up to date or somehow migrate?
>
> The update should be automatic by these lines:
> https://www.fossil-scm.org/fossil/artifact/e094c603?ln=81-85
>
> I don't know why it is not working for you.
I ran into the same thing last week as well, with very old repo.
My workaround was to use a high 1.x version of fossil (*) and use that
to `fossil rebuild`. This updated the schema and after that my fossil
2.4 was able to handle the repo too.
(*) I still had 1.37 around, and now I am keeping that version for
some time longer.
I suspect that something about (old) schema updates does not work
across the 1.x / 2.x border.
> Possible work-around:
>
> Run: fossil sql $yourrepo
> Enter: ALTER TABLE config ADD COLUMN mtime INTEGER;
> Then: UPDATE config SET mtime=now();
>
> Let me know if that helps.
--
See you,
Andreas Kupries <[email protected]>
<http://core.tcl.tk/akupries/>
Developer @ SUSE (MicroFocus Canada LLC)
<[email protected]>
-------------------------------------------------------------------------------
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
