Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#1786 closed enhancement (fixed)

Create one log entry for every changed property instead of building a comma-separated summary

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: major Milestone: BASE 3.3
Component: core Version:
Keywords: Cc:

Description

This is related to #1784 and is a first step for making it possible to implement logging of old values. This is also related to #1753 and will make it easier to implement the requirement to ignore changes to AnnotationSet.itemId simply by annotating it with @NotLoggable (see #1785).

Change History (3)

comment:1 Changed 8 years ago by Nicklas Nordborg

Owner: changed from everyone to Nicklas Nordborg
Status: newassigned

comment:2 Changed 8 years ago by Nicklas Nordborg

Resolution: fixed
Status: assignedclosed

(In [6349]) Fixes #1786: Create one log entry for every changed property instead of building a comma-separated summary

The old methods for generating change log entries in EntityDetails have been deprecated and replaced with new that can generate a list of change log entries instead. A list if of course only generated if the 'changelog.dblogger.detailed-properties' flag is enabled. Otherwise only a single entry is generated.

Also includes a cleaner fix for #1753 which now can take advantage of the @NotLoggable annotation created in #1785.

comment:3 Changed 7 years ago by Nicklas Nordborg

(In [6510]) References #1786: Create one log entry for every changed property instead of building a comma-separated summary

Use ADD and REMOVE change type instead of CREATE/DELETE for changes that are not made on the main item. For example, when adding an annotation or data file to an item.

Note: See TracTickets for help on using tickets.