StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
842137
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-05-08T22:46:25.410
FavoriteCount
0
LastActivityDate
2009-05-08T22:46:25.410
LastEditDate
LastEditorUserId
0
OwnerUserId
51209
ParentId
790693
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
If only there were some kind of view inheritance... So that one can subclass controller without need to supply all its views. Good thing is that there is this <a href="http://dev.rubyonrails.org/ticket/7076" rel="nofollow noreferrer">patch</a>. Bad thing is that it can't make it to the core for quite a while. Having applied it to my rails 2.2, I managed to have the following answer to the original question. Subclassing controller ProductController has been blessed with the twins: <pre><code>class Products::AdminController < ProductsController layout 'admin' before_filter :authenticate end </code></pre> and <pre><code>class Products::StoreController < ProductsController layout 'store' before_filter :find_cart end </code></pre> This itself looks quite nice since each of them as well carries its own initialization part. Changing routes <pre><code> map.resources :products, :controller => 'products/admin', :path_prefix => 'admin', :name_prefix => 'admin_' map.resources :products, :controller => 'products/store', :path_prefix => 'store', :only => [:show, :index], :name_prefix => 'store_' </code></pre> Not an easy route, defo. But, hey, after this point everything just works (assuming you fixed path helpers) with ProductController views and partials. Shared views changes Each subclass controller has its own version of index.html.erb. Everything else is shared in a base class. Speaking about path helpers in shared templates. What used to be <pre><code><% form_for @product ... %> </code></pre> becomes <pre><code><% form_for [controller_name, @product] ... %> </code></pre> and thins like <pre><code><%= link_to products_path %> </code></pre> turn into <pre><code><%= link_to send("#{controller_name}_products_path") %> </code></pre> I don't know if it is all worth it, but that is a way. Anyone knows why if there are plans to include this patch in rails soon?
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POconditional view/layout
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USartemave
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.