Index: openacs-4/packages/xotcl-request-monitor/xotcl-request-monitor.info
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-request-monitor/xotcl-request-monitor.info,v
diff -u -N -r1.15.2.8 -r1.15.2.9
--- openacs-4/packages/xotcl-request-monitor/xotcl-request-monitor.info 21 Nov 2020 23:55:24 -0000 1.15.2.8
+++ openacs-4/packages/xotcl-request-monitor/xotcl-request-monitor.info 11 Dec 2020 16:31:17 -0000 1.15.2.9
@@ -8,7 +8,7 @@
t
request-monitor
-
+
Gustaf Neumann
WU Vienna
Request Monitor with user tracking functionality
@@ -33,8 +33,7 @@
BSD-Style
2
-
-
+
Index: openacs-4/packages/xotcl-request-monitor/sql/postgresql/upgrade/upgrade-0.60-0.61.sql
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-request-monitor/sql/postgresql/upgrade/Attic/upgrade-0.60-0.61.sql,v
diff -u -N
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ openacs-4/packages/xotcl-request-monitor/sql/postgresql/upgrade/upgrade-0.60-0.61.sql 11 Dec 2020 16:31:17 -0000 1.1.2.1
@@ -0,0 +1,3 @@
+
+ALTER TABLE IF EXISTS request_monitor_community_activities
+DROP CONSTRAINT IF EXISTS request_monitor_community_activities_community_id_fkey;
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 -N -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