From ca263834e93814105ca9ea77ab213cff0bc95faa Mon Sep 17 00:00:00 2001
From: Ellie Huxtable <ellie@elliehuxtable.com>
Date: Wed, 17 May 2023 21:28:37 +0100
Subject: Restructure account commands to account subcommand (#984)

* Stop running triggers on history delete

* Move to account management dir

* Alter trigger function to only run for inserts

* wip

* Add atuin account subcommands, and re-org delete

* Clarify docs

* Delete silly dupe migration

* Um where did this come from

* Oops, insert only plz
---
 .../20230515221038_trigger-delete-only.sql         | 30 ++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 atuin-server/migrations/20230515221038_trigger-delete-only.sql

(limited to 'atuin-server')

diff --git a/atuin-server/migrations/20230515221038_trigger-delete-only.sql b/atuin-server/migrations/20230515221038_trigger-delete-only.sql
new file mode 100644
index 000000000..3d0bba528
--- /dev/null
+++ b/atuin-server/migrations/20230515221038_trigger-delete-only.sql
@@ -0,0 +1,30 @@
+-- We do not need to run the trigger on deletes, as the only time we are deleting history is when the user
+-- has already been deleted
+-- This actually slows down deleting all the history a good bit!
+
+create or replace function user_history_count()
+returns trigger as 
+$func$
+begin
+	if (TG_OP='INSERT') then
+		update total_history_count_user set total = total + 1 where user_id = new.user_id;
+
+		if not found then
+			insert into total_history_count_user(user_id, total) 
+			values (
+				new.user_id, 
+				(select count(1) from history where user_id = new.user_id)
+			);
+		end if;
+	end if;
+
+	return NEW; -- this is actually ignored for an after trigger, but oh well
+end;
+$func$
+language plpgsql volatile -- pldfplplpflh
+cost 100; -- default value
+
+create or replace trigger tg_user_history_count 
+	after insert on history 
+	for each row 
+	execute procedure user_history_count();
-- 
cgit v1.2.3