Modified Hydrators to be per-query instances instead of a singleton-like approach

[guilhermeblanco]

This fixes an old issue we have where we have a Query that triggers an entity-specific postLoad event which attempts to do another Query.
In this situation, developer will face an "Attempt to call method on a null object" error on PHP.

[doctrinebot]

Hello,

thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:

http://www.doctrine-project.org/jira/browse/DDC-2578

We use Jira to track the state of pull requests and the versions they got
included in.

[Ocramius]

@guilhermeblanco was removing API necessary here?

[guilhermeblanco]

@Ocramius it was not used anywhere else.

[Ocramius]

Yes, but it's in an interface...
On 29 Jul 2013 04:10, "Guilherme Blanco" [email protected] wrote:

@Ocramius https://github.com/Ocramius it was not used anywhere else.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/738#issuecomment-21696267
.

[guilhermeblanco]

@Ocramius which got created only on master because of EntityManagerDecorator (one of my modified files).

[Ocramius]

Ah, wasn't aware of that. Nothing to argue about then :)
On 29 Jul 2013 04:14, "Guilherme Blanco" [email protected] wrote:

@Ocramius https://github.com/Ocramius which got created only on master
because of EntityManagerDecorator (one of my modified files).

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/738#issuecomment-21696362
.

[beberlei]

this is a BC break, people are using this. You should delegate that call to newHydrator.

[Ocramius]

@beberlei the API is not existing in 2.3.x. Would you still consider it a break since it's in the 2.4.x-RCy?

[beberlei]

@Ocramius err yes of course, BC breaks are only allowed in MAJOR versions, i.e. 2.* => 3.0