StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow do we identify parameters in a dynamic URL?
primarykey
Id
4690298
data
AcceptedAnswerId
4705154
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-01-14T10:57:58.747
FavoriteCount
1
LastActivityDate
2011-01-16T11:52:06.920
LastEditDate
2017-05-23T11:55:28.963
LastEditorUserId
-1
OwnerUserId
81342
ParentId
0
PostTypeId
1
Score
1
ViewCount
881
LastEditorDisplayName
text
Body
We are building a Rails CMS where a blog or news listing can appear anywhere in the site tree. This means that any page knows their type based on a database field - eg: a page knows that it is of type newslisting so once that URL is called for that page we need it to be processed by the newslistingcontroller. The subpages of the newslisting page are news stories - each with a date and category. The URL to the newslisting might be <pre><code>/dogs/snoopy-news/ </code></pre> and a news story might be <pre><code>/dogs/snoopy-news/snoopy-is-great/ </code></pre> The complexity for us is with URLs that have additional parameters in for listing date ranges of news stories or category listings eg: Listing all november news stories <pre><code>/dogs/snoopy-news/2010/11/ </code></pre> Or listing all stories which have food as their category: <pre><code>/dogs/snoopy-news/category/food/ </code></pre> Since that newslisting page could be at any level in the site hierarchy how would we approach identifying that 2010 is a parameter or that category is a parameter? (We will store all URLs in the database for each page so we can lookup first to see if a page exists for a URL) EDIT: This post gives a possible solution: <a href="https://stackoverflow.com/questions/776268/dynamic-cms-like-routes-in-ruby-on-rails">Dynamic CMS like routes in ruby on rails</a> which we will try out and report back on. On save of a page in the CMS we would add routes to the routing table at that point for not only the page itself but for also possible parameters: <pre><code>/dogs/snoopy-news/{year}/{month}/ </code></pre>
Tags
<ruby-on-rails><routing>
Title
How do we identify parameters in a dynamic URL?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USpetenelson
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHow do we identify parameters in a dynamic URL?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POHow do we identify parameters in a dynamic URL?
 UserUserId
 USChristopher Harwood
 VoteTypeVoteTypeId
 VTFavorite
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.