Index: openacs-4/packages/xotcl-request-monitor/tcl/throttle_mod-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-request-monitor/tcl/throttle_mod-procs.tcl,v
diff -u -r1.67.2.34 -r1.67.2.35
--- openacs-4/packages/xotcl-request-monitor/tcl/throttle_mod-procs.tcl	27 Nov 2020 10:33:48 -0000	1.67.2.34
+++ openacs-4/packages/xotcl-request-monitor/tcl/throttle_mod-procs.tcl	11 Dec 2020 16:31:17 -0000	1.67.2.35
@@ -2021,10 +2021,21 @@
     #
     # Data model for per-community / per-subsite activity statistics
     #
+    # we had previously an FK on community_id to acs_objects:
+    #
+    #     community_id {integer references acs_objects(object_id) on delete cascade}
+    #
+    # When a user deletes a community, then also the traces of this
+    # activity in the community will be deleted, allthough the fact
+    # that the users did something there will be flushed as well. This
+    # can be a problem, when communities are created and deleted
+    # frequently. Furthermore, during deletion FK violations might
+    # have appeared for the deleting user.
+    #
     ::xo::db::require table request_monitor_community_activities {
       user_id      {integer references parties(party_id) on delete cascade}
       peer_address text
-      community_id {integer references acs_objects(object_id) on delete cascade}
+      community_id integer
       start_time   timestamptz
       end_time     timestamptz
       clicks       integer