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.
.Notificatie urenschatting gestuurd naar Integrated Marijn (firstname.lastname@example.org)
.Schatting van 2.5 uur is geaccepteerd door Integrated Marijn.
There is no vagrant box available, is going to look into it,.
and/or ignore in ArrayComparer
Values that are not set, are set with "null", so this problem is not present for the first level. This does however not work for values with multiple levels, so this check should be recursive.
Things like empty endDate in PublishTime are stored as ISODate("9999-12-31T00:00:00.000000Z").
thanks for looking into this. here some more input for the "problem definition":
Empty values: agree
Empty DateTime: this issue is a bit more complex: the content history gets the "new" values on the onFlush event. In this event not all "new" values are computed: the preUpdate is event is preformed later on. I think this should be fixed so that all preUpdate values are compared.