Uploaded image for project: 'Doctrine 2 - ORM'
  1. Doctrine 2 - ORM
  2. DDC-33

Remove allowPartialObjects option.


    • Type: Task
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0-ALPHA2
    • Fix Version/s: 2.0-ALPHA3
    • Component/s: ORM
    • Security Level: All
    • Labels:


      I think this option will cause unnecessary confusion. The best solution is to always disallow partial objects, yet you can force partial objects on individual object queries to increase performance if necessary. This is much simpler for the user than to remember all the details of how the current option affects certain behavior. Also, with the current default behavior of partial objects everywhere, some standard operations can unexpectedly not work, like adding an object to a collection of a managed object (but the collection itself was not fetched yet). As a result the collection will not be wrapped by doctrine with a PersistentCollection and modifications are lost.
      There are more of such examples.

      I will do this myself and I think this can even be done with full backwards compatibility (though its not strictly necessary since we're still in alpha).

      This should be done before entering beta.


        There are no comments yet on this issue.


          • Assignee:
            romanb Roman S. Borschel
            romanb Roman S. Borschel
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: