How can I “defang” a Doctrine2 Entity?

If your views don't know about the EM (and they shouldn't), any changes they make to the entities will disappear at the end of the request The only other option I can think of is to hydrate your results as arrays when they're destined to be fed to the view script. But that gives up a lot of handy functionality.

If your views don't know about the EM (and they shouldn't), any changes they make to the entities will disappear at the end of the request. The only other option I can think of is to hydrate your results as arrays when they're destined to be fed to the view script. But that gives up a lot of handy functionality.

I'm not concerned that my views are going to flush anything themselves, but I am worried about the possibility of a controller calling a "getter" API action, making changes to a returned Entity, then calling a second API action that involves flushing the EM. The second API call will write my intended changes, along with any unintended changes made in between API calls. I could, just be careful not to make changes outside of the API, but the point of the API is to protect myself from mistakes, and free the controllers from having to worry about how the Entities are related to the EM.

– Andrew Rueckert Aug 11 at 0:00 Another option is to detach your entities before passing them to a view. Of course, you'll need to take care that A) You've fetched all associations you need, and B) Your detach operation cascades through all the associations. – timdev Sep 2 at 23:26.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.