You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever we have schema change, we need to migrate db.
{"level":"error","ts":1570859268.5242386,"caller":"committee/committee.go:211","msg":"failed to catch up via network","ioAddr":"io1gh439pm67d4cwxt882xpylj75klys6esepml60","networkAddr":"0.0.0.0:4689","height":7826200,"error":"failed to get record hashes: no such column: ids","errorVerbose":"no such column: ids\nfailed to get record hashes\ngithub.com/iotexproject/iotex-election/committee.(*recordTableOperator).Put\n\t/go/pkg/mod/github.com/iotexproject/[email protected]/committee/recordtableoperator.go:184\ngithub.com/iotexproject/iotex-election/committee.(*archive).PutPoll\n\t/go/pkg/mod/github.com/iotexproject/[email protected]/committee/pollarchive.go:185\ngithub.com/iotexproject/iotex-election/committee.(*committee).storeInBatch\n\t/go/pkg/mod/github.com/iotexproject/[email protected]/committee/committee.go:349\ngithub.com/iotexproject/iotex-election/committee.(*committee).Start.func1\n\t/go/pkg/mod/github.com/iotexproject/[email protected]/committee/committee.go:210\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1337"}
The text was updated successfully, but these errors were encountered:
it seems same issue with #117
Because we changed the table schema with same table name between v0.2.2 and v0.2.7. Can we remove the db(new sqlite DB, not old one) and migrate again just for testNet? Or we should find out other way
Whenever we have schema change, we need to migrate db.
The text was updated successfully, but these errors were encountered: