DDC-3263: setFetchmode for ClassMetaData temorarily instead of Query #4037

Closed
opened 2026-01-22 14:34:09 +01:00 by admin · 2 comments
Owner

Originally created by @doctrinebot on GitHub (Aug 21, 2014).

Originally assigned to: @Ocramius on GitHub.

Jira issue originally created by user adyballa:

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.

Originally created by @doctrinebot on GitHub (Aug 21, 2014). Originally assigned to: @Ocramius on GitHub. Jira issue originally created by user adyballa: 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.
admin added the Improvement label 2026-01-22 14:34:09 +01:00
admin closed this issue 2026-01-22 14:34:09 +01:00
Author
Owner

@doctrinebot commented on GitHub (Oct 19, 2014):

Comment created by @ocramius:

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.

@doctrinebot commented on GitHub (Oct 19, 2014): Comment created by @ocramius: 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.
Author
Owner

@doctrinebot commented on GitHub (Oct 19, 2014):

Issue was closed with resolution "Won't Fix"

@doctrinebot commented on GitHub (Oct 19, 2014): Issue was closed with resolution "Won't Fix"
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#4037