mahara-contributors team mailing list archive

[Mahara Bot <1692385@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/7775
Committed: https://git.mahara.org/mahara/mahara/commit/ebd928b11e79c0054133b284c2a49bb8a86d3a2f
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    master

commit ebd928b11e79c0054133b284c2a49bb8a86d3a2f
Author: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
Date:   Tue May 23 12:55:41 2017 +1200

Bug 1692385: Adjusting the event_log table

Add 5 new new columns to event_log table make searching over the
data easier and also record the id of any parent/related info as well

Eg, if one deletes an image block from a page we now record:
id - the event id
resourceid - the block id
resourcetype - the blocktype, eg image
parentresourceid - the id of the parent, eg view id
parentresourcetype - the type of parent, eg 'view'

Because we would not be able to find related view info from just the
block id anymore.

Also added the ability to index and search over event information in
elasticsearch search type event_log

Change-Id: I280c1c75c35a6c58f42d8acb36cf5c24c70b902d
Signed-off-by: Robert Lyon <robertl@xxxxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1692385

Title:
  Adjust the event_log table to facilitate logging of more chronological
  information

Status in Mahara:
  Fix Committed

Bug description:
  Currently for a number of things we only record the creation time
  (ctime) and last time they were interacted with (mtime). For views we
  also record last accessed time (atime).

  It would be better if we recorded the changes over time for things.

  So will add some _logging tables to record this info

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1692385/+subscriptions