feat: create an analytics_summary database view for analytics (take…

… two) (#2473)

hasura.planx.uk/metadata/tables.yaml

@@ -64,6 +64,9 @@
           - user_exit
         filter: {}
         check: null
+- table:
+    schema: public
+    name: analytics_summary
 - table:
     schema: public
     name: blpu_codes

hasura.planx.uk/migrations/1700671079904_create_analytics_summary_view/down.sql

@@ -0,0 +1 @@
+DROP VIEW public.analytics_summary CASCADE;

hasura.planx.uk/migrations/1700671079904_create_analytics_summary_view/up.sql

@@ -0,0 +1,22 @@
+CREATE OR REPLACE VIEW public.analytics_summary AS 
+select 
+	a.id as analytics_id,
+	al.id as analytics_log_id,
+	f.slug as service_slug,
+	t.slug as team_slug,
+	a.type as analytics_type,
+	a.created_at as analytics_created_at,
+	user_agent,
+	referrer,
+	flow_direction,
+	metadata,
+	al.user_exit as is_user_exit,
+	node_type,
+	node_title,
+	has_clicked_help,
+	input_errors,
+	CAST(EXTRACT(EPOCH FROM (al.next_log_created_at - al.created_at)) as numeric (10, 1)) as time_spent_on_node_seconds
+from analytics a
+	left join analytics_logs al on a.id = al.analytics_id
+	left join flows f on a.flow_id = f.id
+	left join teams t on t.id = f.team_id;