One are that could probably be improved is auto including associations when permissions checks always require the association. Example is the chain from task to story to project in the agility tutorial. A view check of a task will always require both the story it belongs to and the story's project. It wouldn't be an unreasonable assumption that loading a task (or multiple tasks) would require checking the view permission at some point and thus eager loading the given associations wouldn't be out of order.
I'm not sure if any of the other permissions have a strong enough indication of likely loading to warrant eager loading. The other possibility I can think of would be useful in production mode, adapting initial loads for a particular controller/action based off what gets loaded after the controller. DRYML tends to blur the line between view and controller and sometimes it makes it quite difficult to keep it from making extra DB calls in the view. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
