http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DC-280 Doctrine 1 <p>Over the last several weeks I've been working on streamlining the access control logic in the application I'm working on, and I realized that Doctrine's event listeners might be able to help. For more detailed background information take a look at <a href="http://groups.google.com:80/group/dallasphp/browse_thread/thread/91e3f107cd611adf" class="external-link">http://groups.google.com:80/group/dallasphp/browse_thread/thread/91e3f107cd611adf</a> ...but here's the problem in a nutshell:</p> <p>Since my application's access control logic is all implemented in PHP rather than in the database (i.e., I can't add access control to my queries as a simple WHERE clause), I'm looking for a way to hook into the query process just after the records have been hydrated and actually modify the result set that gets returned, such that only permissible records show up in the final result set.</p> <p>Unfortunately, although there are several listener methods that look promising for this, none of them seem to have access to the data being returned. For instance, if I run a custom query via Doctrine_Query::execute(), the postQuery() hook definitely runs ...but it doesn't give me access to anything but the query string itself.</p> <p>Since, in some instances (e.g., hydration listeners), the Doctrine_Event object is assigned arbitrary data that the listener can modify, I'm wondering if the same thing couldn't be done more universally?</p> DC-280

Add pre/postHydrateResultSet() events

New Feature Major Open Unresolved Jonathan H. Wage Adam Jensen Mon, 23 Nov 2009 23:38:02 +0000 Tue, 8 Jun 2010 16:09:38 +0000 Connection Query Record 0 1 <p>In Doctrine 1.2 you can create custom hydrators. You can extend the core hydrators to remove the data you want? I think that would work.</p> <p>Sure enough, that does the trick!</p> <p>There are a couple of downsides, though, that might be worth considering in terms of future development:</p> <p>1. It would be nice to be able to specify constructor arguments for the hydrator, so that collaborators can be injected. In my example, the hydrator needs access to the application's access control list object; currently it's simply retrieving it from a global registry, but it would be nice for testing's sake to be able to inject it instead.<br/> 2. It would also be nice to be able to chain multiple hydrators together; that's one reason I was looking at listeners, since they've got that capability already. That approach allows you to keep distinct behavior distinct a lot more easily.</p> <p>Ultimately, I'd still kind of like to see another listener method available ...say, preHydrateResultSet() and postHydrateResultSet()? I think that would be a more flexible approach, even though the custom hydrator solution works quite well.</p> <p>Thanks!<br/> Adam</p> <p>I like the idea. I'll move this to 1.3. I don't think we're gonna have a 1.3 version but if we do, it'll be there.</p> <p>We can include this in a 1.2.x release if you would like to provide a patch and some tests. Thanks, Jon</p>