From 528f8f18a6aa35869cdb78861094811f2146d997 Mon Sep 17 00:00:00 2001
From: peinz <s8923496@stud.uni-frankfurt.de>
Date: Fri, 18 Apr 2025 08:49:25 +0000
Subject: [PATCH] fix: view-update should only get parentIDs from own
collection
---
modules/materialized-views/server/view-manager.ts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/modules/materialized-views/server/view-manager.ts b/modules/materialized-views/server/view-manager.ts
index 3d37cd2092..3ea1a99efb 100644
--- a/modules/materialized-views/server/view-manager.ts
+++ b/modules/materialized-views/server/view-manager.ts
@@ -226,7 +226,7 @@ async function startDBChangeListening() {
// ids which need to be updated because itself has changed.
// We need this, because there could be an dbIdChanged which itself does not have a materialized view. In this case this array would be empty as the _id has no corresponding index
const updateDirectIdsForView = [
- ...new Set(toUpdateIndices.filter(u => u.parentId === dbIdChanged).map(d => d.parentId)),
+ ...new Set(indicesForView.filter(u => u.parentId === dbIdChanged).map(d => d.parentId)),
];
// handle different updates
--
GitLab