Ok, so I made a beginner coding error in a token contract, mis-typing the return value from get
without &
(yes, I now see the Warning in the docs at https://developers.eos.io/manuals/eosio.cdt/latest/classeosio_1_1multi__index/#function-get) and wound up with a corrupted stat table. I can't erase it because it no longer matches the abi table definitions and accessing it throws an error.
The only thing I have thought of is to reverse-engineer a table declaration under which the corrupted table is readable, then upload code which does an erase
loop using that.
Using the chain API get_table_rows
I get the following response from the corrupted table:
"rows":["0100000000000000000000000000000004534545445300000070520a83a920cdc0e94558d1339db9"]
Any suggestions for a suitable table declaration? Or am I on the wrong track?
internal_use_do_not_use::db_lowerbound_i64
;)