This is what owner associations were designed to handle. Tutorial here:
http://cookbook.hobocentral.net/tutorials/agility#project-belongs-to-user
Bryan
[email protected] wrote:
Ok, so is that to say that I need to add back in all of the default
rails CRUD stuff to my controllers so that I can access records only
of the current user for each CRUD operation? Seems to be a bit
counterproductive since hobo moved all of the CRUD stuff out of the
controller and into my models (or at least that's how I perceive it
works).
Is there a more complete example on how to do this hobo style? I think
it is a common design goal in a web application to restrict users to
only be able to access their own set of data. lA very simple tutorial
or sample app would go a long ways here :-)
--jeremy
On Apr 7, 3:09 am, Tom Locke <[email protected]> wrote:
Previously in my tasks
controller I would do something like:
def index
@tasks = current_user.tasks.all
You can do exactly that - it will work. However you will lose some of the
benefits such as automatic pagination and checking of view permission.
You can also do
def index
hobo_index current_user.tasks
end
Tom
--
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.
