new db column for the storage of a full address

[nicarq]

After https://github.com/Emurgo/project-icarus-importer/pull/4 we are limiting the addresses storage to a maximum of 2k. No matter what is going to be the ”final” size of the address, probably we want to store it anyways.

We should create a new column (non-indexable) that stores any size address. I think this information is going to come handy in the near-future.

Question: should we store the full address for all the addresses or for only the ones that go over the limit?

• Maybe the priority would be the difficulty of the implementation for the options. No matter that the latter one is more efficient with space .

[vsubhuman]

should we store the full address for all the addresses or for only the ones that go over the limit

If not create a separate table just for these cases - then I would definitely argue for storing full versions only for these long addresses.

But I would think of creating a separate table like (short_address text, full_address text), and the first one may be indexed.