Yeah… I’m totally struggling to grok resource routes too… seems like
they’ve totally blown the beautiful simplicity of the old url pattern
stuff out of the water.
Would love to hear an answer to this question!!!
Andy T. wrote:
I want to customize map.resources so it uses a uid in the URL instead
of the database id. The uid is a field on my object.
So I have map.resources :things in routes.rb and I can update a thing
by accessing POST /thing/1. Instead I want to update the thing by
POST /thing/80ed14ce098affc2 The thing has an id of 1 and a uid of
Any options other then getting rid of map.resources and explicitly
defining all the REST routes?
Found a solution and that is to override to_param on each of the
objects, so in the thing model I have
Then in things_controller I have
@thing = Thing.find_by_uid(params[:id])
There’s also a patch out at http://dev.rubyonrails.org/ticket/6814,
which allows you to use map.resources :things, :key => :uid and that
way you could just use
in your controller.
On 2/9/07, Andy T. [email protected] wrote:
Just to make it clear, there’s nothing in the resource routes that
prevent you from using an alternate field. It all has to do with what
your controllers expect to find in the params[:id] parameter.