StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14683718
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-04T09:23:57.490
FavoriteCount
0
LastActivityDate
2013-02-04T09:23:57.490
LastEditDate
2017-05-23T12:18:30.317
LastEditorUserId
-1
OwnerUserId
213002
ParentId
2596312
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
As suggested in the question <a href="https://stackoverflow.com/questions/4207657/rails-routing-to-handle-multiple-domains-on-single-application">Rails routing to handle multiple domains on single application</a>, I guess you could use <a href="http://guides.rubyonrails.org/routing.html#advanced-constraints" rel="nofollow noreferrer">Rails Routing - Advanced Constraints</a> to build what you need. If you have a limited space of controllers (with unlimited views pointing to them), this should work. Just create a constraint for each controller that verifies if the current view matches them. Assuming you have a space of 2 controllers (PostController and CommentController), you could add the following to your routes.rb: <pre><code>match "*path" => "post#show", :constraints => PostConstraint.new match "*path" => "comment#show", :constraints => CommentConstraint.new </code></pre> Then, create lib/post_constraint.rb: <pre><code>class PostConstraint def matches?(request) 'post' == Rails.cache.fetch("/view_controller_map/#{request.params[:view_name]}") { View.find_by_name(request.params[:view_name]).controller } end end </code></pre> Finally, create lib/comment_constraint.rb: <pre><code>class CommentConstraint def matches?(request) 'comment' == Rails.cache.fetch("/view_controller_map/#{request.params[:view_name]}") { View.find_by_name(request.params[:view_name]).controller } end end </code></pre> You can do some improvements, like defining a super constraint class that fetches the cache, so you don't have to repeat code and don't risk fetching a wrong cache key name in one of the constraints.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODynamic URL -> Controller mapping for routes in Rails
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USbarbolo
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.