Greetings,
Due to some ill-conceived advice and over-enthusiastic scripting, I
managed to execute a command like this:
fossil ticket set e9d34a2552 +icomment "ivenkat added on
2016-10-21.18:50:20 PDT:<br>
script checked in to [1a8ae0e34f]"
This failed with
SQLITE_ERROR: table ticketchng has no column named +icomment
fossil: table ticketchng has no column named +icomment
INSERT INTO
ticketchng(tkt_id,tkt_mtime,"+icomment",tkt_rid)VALUES(272,:mtime,..
No problem. I fixed my command. But this broke all syncs. A rebuild
of the db comes back with the same error:
ivenkat@a4x128-05 sdc]$ fossil rebuild
98.0% complete...
SQLITE_ERROR: table ticketchng has no column named +icomment
fossil: table ticketchng has no column named +icomment
INSERT INTO ticketchng(tkt_id,tkt_mtime,"+icomment",tkt_rid)VALUES(...
Another DB that was sync'ing with this also fails to sync:
fossil sync
Sync with http:// <deleted>
Round-trips: 1 Artifacts sent: 0 received: 2
SQLITE_ERROR: table ticketchng has no column named +icomment
fossil: table ticketchng has no column named +icomment
INSERT INTO
ticketchng(tkt_id,tkt_mtime,"+icomment",tkt_rid)VALUES(239,:mtime,'{
This is fossil version 1.35 [d8d2222b91] 2016-01-17 22:12:21 UTC
My checkins on other sites have now halted :O.
I tried to find where that +icomment was coming from without much success.
Any advice appreciated. Fossil sqlite3 hackery is fine.
Thanks
-Venkat
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
