More `/v2/actions` improvements

Huginn Ravenrequested to merge
feature-actions into develop
  • Clean up some error messages
  • Look up heights for actions with an SQL JOIN

This later one is a preventative measure to avoid potentially unbound timestamp->height selects for an action range. (Say, for a specific address, where a limited amount of actions can be spread across an arbitrary time range.)

I found an example where an actions query fetches > 300000 rows from the DB to determine height for ~30 actions. (Withdraws for address thor12z5yppemc6ye3ln6r43wuw3nk6k70xtg52qcms.)

Merge request reports