Lazy-loading properties not loading in Doctrine 2.0?

As seen above in my question, I've added the fetch="EAGER" attribute to the relational annotation, and now everything seems to go just fine (except for the fact that loading is no longer lazy) This is of course a workaround, and no fix of the actual bug. In addition to this, I still don't know what caused my code/Doctrine to break. However, the performance impact of this workaround seems to be negligible - if even present at all.

As seen above in my question, I've added the fetch="EAGER" attribute to the relational annotation, and now everything seems to go just fine (except for the fact that loading is no longer lazy). This is of course a workaround, and no fix of the actual bug. In addition to this, I still don't know what caused my code/Doctrine to break.

However, the performance impact of this workaround seems to be negligible - if even present at all.

It looks like internal d2 bug. Or you use reflection to retrieve properties of your object. Proxy classes use persister to initialize them on any method call.

Does it issue a query when you use getter on this proxy?

1 because this is not an answer to my question - I will, however, expand my question/answer to include this (well documented) information. – pepijn Oct 19 at 12:33 if I get an answer to my problem i'll let you know :) – Andrew 'lionel' Fenna Oct 19 at 16:21.

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.