Bug #6581

Updated objects considered new, causing exception

Added by Karsten Dambekalns over 5 years ago. Updated almost 5 years ago.

Status:Resolved Start date:2010-02-24
Priority:Must have Due date:
Assigned To:Karsten Dambekalns % Done:

100%
Category:Persistence
Target version:TYPO3 Flow Base Distribution - 1.0 alpha 8
PHP Version: Complexity:
Has patch: Affected Flow version:

Description

When updated objects are to be persisted but seen through a property of another object first a "new" object is "seen" by the persistence layer and results in the same identifier being used twice in the underlying database (leading to a constraint violation).

Associated revisions

Revision 616762ca
Added by Karsten Dambekalns over 5 years ago

[+BUGFIX] FLOW3 (Persistence): Fixed a bug with persistence that hit when updated objects were to be persisted but seen through a property of another object first (order of persistObject calls). Fixes #6581, relates to #4931.

History

#1 Updated by Karsten Dambekalns over 5 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r3851.

Also available in: Atom PDF