Once we have [a new test document format]() and a new table with those documents stored inside, we will need to make the view-report web app use the new document format. This should improve its performance a little bit, and is necessary for us to be able to delete the old, compressed database.
The JSON version of the view-report must still use the old JSON format, however. The necessary routines for converting to the old Metabase::Fact JSON format should be located in the schema project.
The view-report.cgi replacement should try to look for the JSON report in the new test reports table first. If it's there, use that one. If it's not, look in the old Metabase cache.
Once we have [a new test document format]() and a new table with those documents stored inside, we will need to make the view-report web app use the new document format. This should improve its performance a little bit, and is necessary for us to be able to delete the old, compressed database.
The JSON version of the view-report must still use the old JSON format, however. The necessary routines for converting to the old Metabase::Fact JSON format should be located in the schema project.
The view-report.cgi replacement should try to look for the JSON report in the new test reports table first. If it's there, use that one. If it's not, look in the old Metabase cache.