Doctrine 2 - ORM

Persisting Entities with unmanaged related associations produces ugly notices

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-BETA1
  • Fix Version/s: 2.0-BETA3
  • Component/s: ORM
  • Security Level: All
  • Labels:
    None

Description

It often happens that you forget to persist related entities during development, producing ugly notices about $object hash not being part of certain arrays, for example in "getEntityIdentifier".

Maybe this can be gracefully intercepted without cluttering the code?

Issue Links

is referenced by

Improvement - An improvement or enhancement to an existing feature or task. DDC-718 Bottleneck in computeAssociationChanges()?

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

There are no comments yet on this issue.

People

  • Assignee:
    Roman S. Borschel
    Reporter:
    Benjamin Eberlei
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: