Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-3263

setFetchmode for ClassMetaData temorarily instead of Query

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 2.2
    • Fix Version/s: None
    • Component/s: DQL, Mapping Drivers
    • Security Level: All
    • Labels:
      None

      Description

      SetFetchmode is now woriking in AbstractQuery.

      Why dont implement setFetchMode and perhaps further temporarily changes in an ClassMetadata-managing Object. Perhaps to work with a temporarily copy to allow a reset after some action.

        Activity

        Hide
        Marco Pivetta added a comment -

        Contextual changes in the entire UoW can lead to hard to predict situation that we don't want nor need to implement, as they represent additional complexity.

        Show
        Marco Pivetta added a comment - Contextual changes in the entire UoW can lead to hard to predict situation that we don't want nor need to implement, as they represent additional complexity.

          People

          • Assignee:
            Marco Pivetta
            Reporter:
            Andreas Dyballa
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: