Doctrine MongoDB ODM

recomputeSingleDocumentChangeSet does not work for collections

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: UnitOfWork
  • Labels:
    None

Description

If you have a document with a collection, during computation of the changeSet before persist a reference to that collection is placed in originalData, not a copy. Therefore, if you change the collection in an onFlush event listener, then call recomputeSingleDocumentChangeSet, the changes to the collection are not recognised, because the originalData has changed also.

I will create a test, and hopefully fix for this soon.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tim Roediger added a comment -

PR open with fix https://github.com/doctrine/mongodb-odm/pull/336

Show
Tim Roediger added a comment - PR open with fix https://github.com/doctrine/mongodb-odm/pull/336
Hide
Permalink
Tim Roediger added a comment -

PR merged

Show
Tim Roediger added a comment - PR merged
Tim Roediger made changes -
Field Original Value New Value
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
  • Request to http://www.doctrine-project.org/fisheye/ failed: Error in remote call to 'FishEye 0 (http://www.doctrine-project.org/fisheye/)' (http://www.doctrine-project.org/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=MODM-166, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)

People

  • Assignee:
    Jonathan H. Wage
    Reporter:
    Tim Roediger
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: