From b16cd39aa622f018e318ebef2006c517708cf06e Mon Sep 17 00:00:00 2001
From: Paul-Christian Volkmer
Date: Tue, 23 Jun 2026 14:47:18 +0200
Subject: feat: support for asynchronous follow-up count calculation (#300)

This is required if async messaging is used. The request is already gone if response gets processed.

Workflow:

* Keep old followup_count
* Add expected_followup_count
* If: DNPM:DIP accepts the request - copy to to followup_count
* Else: keep old followup_count

This prevents from saving unaccepted follow-up counts.---
 .../resources/db/migration/mariadb/V0_16_3_1__ExpectedFollowUpCount.sql | 2 ++
 1 file changed, 2 insertions(+)
 create mode 100644 src/main/resources/db/migration/mariadb/V0_16_3_1__ExpectedFollowUpCount.sql

(limited to 'src/main/resources/db/migration/mariadb')

diff --git a/src/main/resources/db/migration/mariadb/V0_16_3_1__ExpectedFollowUpCount.sql b/src/main/resources/db/migration/mariadb/V0_16_3_1__ExpectedFollowUpCount.sql
new file mode 100644
index 0000000..ded8172
--- /dev/null
+++ b/src/main/resources/db/migration/mariadb/V0_16_3_1__ExpectedFollowUpCount.sql
@@ -0,0 +1,2 @@
+ALTER TABLE request ADD COLUMN expected_followup_count int DEFAULT 0;
+UPDATE request SET expected_followup_count = -1;
\ No newline at end of file
-- 
cgit v1.2.3