how to get value from `act_data` in `action_trace` table for act_name='transfer'? about history-tools

[tbfleming]

fill-pg leaves it in binary to save space and to save fill time. JSON conversion expands the size by large factor. Some applications work better with data in its binary format; e.g. wasm-ql. Applications which need the data in json, but only need a small subset (e.g. transfers) are better off not having the overhead of the remaining data converted to json.

If the database will only be used by apps which need a small subset of the data, then a custom-written filler that works in place of fill-pg will probably be a better match.

[tbfleming]

You need to use an abi deserializer, such as abieos or eosjs

[salisbury-espinosa]

@tbfleming maybe it makes sense to save the result of this action immediately in storage (postgresql) when filling out the scheme?

[salisbury-espinosa]

@tbfleming

You need to use an abi deserializer, such as abieos or eosjs

hm, i just tried eosjs (rawAbiToJson method) - dont work

[tbfleming]

rawAbiToJson converts an abi, not action data

[salisbury-espinosa]

converts an abi, not action data

so
how parse act_datain action_trace table to fetch payload?
example from mongodb plugin: EOSIO/eos#4968 (comment)
how can I understand what happened in this action? (for example, how many tokens are transfered)

[salisbury-espinosa]

@tbfleming if I understood everything correctly, it is necessary to retrieve this data before inserting it into the database using this method:

https://github.com/EOSIO/eos/blob/master/libraries/chain/include/eosio/chain/controller.hpp#L273

otherwise, will have to add a column action_data_deserialized in the table + for each trace to call and update it in the background by
https://github.com/EOSIO/eosjs/blob/master/src/eosjs-serialize.ts#L1085
export function deserializeActionData