For withdrawn_at, the reason we're pulling it is because history in prod is a little bit unpredictable. I have seen instances where it is just the number 3 (it doesn't seem to be THE issue), but ultimately, when retrieving participants, the error cannot call jsonb_to_recordset on a non-array often comes up. Hence, removing this from the view.
The report is being removed for now in lieu of providing some SQL to CGI to retrieve this report. Why: when this was clicked in production with 60k+ rows, it just hung. Then the database ballooned in memory and crashed. This makes me suspect that the reports are related to the ballooning memory issue we have had.
We have to pull two features.
For withdrawn_at, the reason we're pulling it is because
history
in prod is a little bit unpredictable. I have seen instances where it is just the number3
(it doesn't seem to be THE issue), but ultimately, when retrieving participants, the errorcannot call jsonb_to_recordset on a non-array
often comes up. Hence, removing this from the view.The report is being removed for now in lieu of providing some SQL to CGI to retrieve this report. Why: when this was clicked in production with 60k+ rows, it just hung. Then the database ballooned in memory and crashed. This makes me suspect that the reports are related to the ballooning memory issue we have had.