Content
View differences
Updated by Klaus Zanders 4 days ago
We have migrated cost reporting to `PersistedQuery` and `PersistedView`. The `cost_queries` table in the database is kept around as a backup if something in the migration goes wrong. Once we have ensured the migration to 18.0 went through fine, we can drop the table.
Note: On `edge` and developer systems that already migrated to the `dev` branch, the table is already gone, so when we add the migration we can use `drop_table :cost_queries, if_exists: true`
Note: On `edge` and developer systems that already migrated to the `dev` branch, the table is already gone, so when we add the migration we can use `drop_table :cost_queries, if_exists: true`