From 9eae5f980d3b6f85d2b464aeab612c1dd9e65467 Mon Sep 17 00:00:00 2001
From: Jon Betts <jon.betts@hypothes.is>
Date: Thu, 15 Jun 2023 16:46:06 +0100
Subject: [PATCH] Ensure we remove the annotation sub type enum when we
 recreate it

---
 .../07_annotation_type_group_counts/01_create_view.sql        | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/h/data_tasks/report/create_from_scratch/07_annotation_type_group_counts/01_create_view.sql b/h/data_tasks/report/create_from_scratch/07_annotation_type_group_counts/01_create_view.sql
index 0140a40e59d..c6bc5158bc5 100644
--- a/h/data_tasks/report/create_from_scratch/07_annotation_type_group_counts/01_create_view.sql
+++ b/h/data_tasks/report/create_from_scratch/07_annotation_type_group_counts/01_create_view.sql
@@ -1,4 +1,4 @@
-DROP MATERIALIZED VIEW IF EXISTS report.annotation_type_group_counts CASCADE;
+DROP TYPE IF EXISTS report.annotation_sub_type CASCADE;
 
 CREATE TYPE report.annotation_sub_type AS ENUM (
     -- This is not a good name for a sub-type of an annotation, we should
@@ -8,6 +8,8 @@ CREATE TYPE report.annotation_sub_type AS ENUM (
     'reply', 'highlight', 'page_note'
 );
 
+DROP MATERIALIZED VIEW IF EXISTS report.annotation_type_group_counts CASCADE;
+
 -- There are various indicators of different sub-types of annotation, only
 -- certain combinations should happen together. This table shows all
 -- combinations and how we will interpret them.