Databases
StackOverflow2013
Postsdbo
PORails Nested resource access problem in resource_controller
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails Nested resource access problem in resource_controller
    primarykey
    data
    text
    <p>I using the Rails resource_controller plugin. I have a ReleasesController, which is nested within a UsersController and a ProjectsController.</p> <p>Resource_controller fails when it attempts to pull the release from User, but succeeds from Project. The problem under User is finding the Release results in an object of type, Enumerable::Enumerator, and not a Release. The same process to find a Release under Project results in identifying the correct Release instance.</p> <p>Digging through the r_c code, I've figured out the net methods calls, which I've duplicated the problem within script/console:</p> <pre><code>&gt;&gt; Project.first.releases.find 17 =&gt; #&lt;Release id: 17, project_id: 1, name: "FORTEEN", lock_version: 10, deleted_at: nil, created_at: "2009-06-22 17:56:10", updated_at: "2009-06-22 19:48:47"&gt; &gt;&gt; User.first.releases.find 17 =&gt; #&lt;Enumerable::Enumerator:0x599e29c&gt; </code></pre> <p>Any Release method used on the Enumerable::Enumerator fails, of course. Here are the definitions of the releases methods:</p> <pre><code>User: def projects # active is a named_scope on Project employer ? employer.projects.active : Project.active end def releases projects.collect { |p| p.releases }.flatten end Project: has_many :releases, :dependent =&gt; :destroy </code></pre> <p>I use the User.projects method in the ProjectsControler without difficulty. I suspect the issue lies with the definition of the User.releases method, but appreciate suggestions on how to fix.</p> <p>Here are my route definitions:</p> <pre><code> map.resources :projects do |project| project.resources :releases, :member =&gt; { :restore =&gt; :get } end map.resources :releases, :member =&gt; { :restore =&gt; :get }, :except =&gt; [ :new, :create ] map.resources :users, :member_path =&gt; '/:id', :nested_member_path =&gt; '/:user_id' do |user| user.resources :projects user.resources :releases, :member =&gt; { :restore =&gt; :get }, :except =&gt; [ :new, :create ] end </code></pre> <p>Thanks! dr</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdr.
    1. USdr.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COIf you show the definition of the routes it could help.
      singulars
      1. PORails Nested resource access problem in resource_controller
      1. USjcoffey
    2. COI'd add that I think the specific issue relates to User.releases returning an actual Array rather than an association proxy, which I think r_c expects.
      singulars
      1. PORails Nested resource access problem in resource_controller
      1. USdr.
    3. CORoute definitions: map.resources :users, :member_path => '/:id', :nested_member_path => '/:user_id' do |user| user.resources :projects user.resources :releases, :member => { :restore => :get }, :except => [ :new, :create ] end map.resources :projects do |project| project.resources :releases, :member => { :restore => :get } end map.resources :releases, :member => { :restore => :get }, :except => [ :new, :create ]
      singulars
      1. PORails Nested resource access problem in resource_controller
      1. USdr.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload