Review main Merged Breaking

65145[!!!][TASK] Remove t3ver_count and t3ver_tstamp db fields

Benni Mack CR +2 V +2 Hard +116 −242 updated 08/03/20, 17:55

Commit message

The patch drops handling and existence of two further
workspaces related db fields:

* t3ver_tstamp has been occassionally set to 'now' when
records in a workspaces were edited. However, the field
was never displayed in the backend and is of little use
since it only holds only a 'last' value. A change
history on workspace records is available through the
'info' button in the workspace module. This is powered
by sys_history and shows modifications with date/time.

* t3ver_count is also never rendered in the backend. It
has been used in the (non-default) 'swap' workspace actions
where live records become the new workspace records. The
field was then incremented by one. The loose wording around
that is, it's an 'archived' record. However, if swapping a
second time, the workspace record does not count two as one
would expect, but still one. Only after another swap, the
workspace record would have the value two in this field.
Together with the fact this field has never been shown/used,
the weird behavior, and that swapping is an uncommon case
that needs to be explicitely enabled and used, the field
is dropped now.

Review

  • Code review CR +2

    Imported before Forger kept the single votes, the next import adds them.

  • Verified V +2

    Imported before Forger kept the single votes, the next import adds them.

Issues 1

Files 20