New data proposals

[telezhnaya]

• State changes https://github.com/near/nearcore/blob/master/core/primitives/src/views.rs#L1681-L1719
• access_key changes: we already have them in access_keys
• DataUpdate, DataDeletion: have no opinion here
• ContractCodeUpdate, ContractCodeDeletion: we may want to create a separate table contracts
• Blocks https://github.com/near/nearcore/blob/master/core/primitives/src/views.rs#L448-L489
• gas_price should contain the other data Do we have correct formula for computing daily_tokens_spent_on_fees?  near-analytics#19
• Chunks https://github.com/near/nearcore/blob/master/core/primitives/src/views.rs#L719-L743
• gas_used, gas_limit should contain the other data Do we have correct formula for computing daily_tokens_spent_on_fees?  near-analytics#19
• Execution outcomes https://github.com/near/nearcore/blob/master/core/primitives/src/views.rs#L1142-L1162
• we need to add execution_outcomes__logs table
• I want to store result https://github.com/near/nearcore/blob/master/core/primitives/src/views.rs#L1032-L1042
• Transactions https://github.com/near/nearcore/blob/master/core/primitives/src/views.rs#L959-L967
• do we want to re-think transaction_actions table? We want at least to write a comment why do we ignore this data
• Receipts https://github.com/near/nearcore/blob/master/core/primitives/src/views.rs#L1374-L1389
• we may want to create 8 separate tables for each ActionView

[telezhnaya]

todo for me:

• create execution_outcomes__logs table
• add smith like result column to execution_outcomes

Open questions:

• gas_price, gas_used, gas_limit
• receipts and 8 corresponding tables

[telezhnaya]

FYI I anyway will implement that on the next iterations since we have the data collected to SingleStore, we will play with the one we've got now