Spike: default value changes are saved to content history

Description

The problem

When a default value for a document is different from the value in the database, the content history detects this as a change. But Doctrine doesn't write the change to the database.

This means it keeps generating records in the content history.

Example 1: phone number in database doesn't have a type

Example 2: reference has wrong db (it would be better to turn storage of $db off, this will be the default in Doctrine ODM 2, http://docs.doctrine-project.org/projects/doctrine-mongodb-odm/en/latest/reference/reference-mapping.html)

Note: also when the changeset is empty a record is sometimes written to the content history.

Environment

None

Deployment actions

None

Technical tasks

None

Status

Assignee

Unassigned

Reporter

Marijn Otte

Client

Integrated Marijn

External issue ID

None

Follow up date

None

Code reviewer

Ger Jan van den Bosch

Developer

Koen Prins

Plan date

None

Max. hours

None

Error message

None

Min. hours

None

Product owner

Marijn Otte

Refiner

None

Switches

None

Dev hour estimate

None

Story Points

1

Time tracking

2h 30m

Epic Link

Sprint

None

Fix versions

Due date

2018/02/01

Priority

Major
Configure