in the time_actions table, there is an issue with how tokens being used in tokenswap contract are being stored. Fix this

[vivekteega]

They aren't being stored like a list ['bioscope', 'rupee']

[vivekteega]

Upon investigation :

In contracts of the type where there is a time action created during the contract creation itself (one-time-event external trigger | one-time-event time trigger), the tokens are stored as a list.

In contracts of the type where the time actions are not defined during the creation of the contract but are defined upon further participation in the contract( continuous event token swap), the tokens_db column is filled depending upon the action being performed.
For eg. In a token swap contract, deposits are time-related actions. For a deposit, there is only 1 associated token during the transaction( the token being deposited). Hence it is being entered without a list.

---

• Until now, the contracts which are being added to time_actions table during the creation itself fall under the categories where only a single token is present. Do we keep it as a list or change it to normal single entry without the list?
• Should all tokenIdentification & token_db columns be stored as lists so it is same across all the devices?