StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
734655
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-04-09T15:09:23.647
FavoriteCount
0
LastActivityDate
2009-04-09T15:09:23.647
LastEditDate
LastEditorUserId
0
OwnerUserId
65070
ParentId
734583
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
To avoid the problems you mention with the static pages (about, home, etc.) you could take a few different aproaches: <ol> <li>Put the dynamic category pages in a separate path (e.g. www.mysite.com/shop/category/page-name-here)</li> <li>Put the static pages in a separate path (e.g. www.mysite.com/pages/about). Now you can't have a category called "pages", but all other ones would work.</li> <li>Put the static routes above the dynamic routes. Not ideal since it could potentially hide category pages if you name your categories poorly, but even if you did #1 or #2, you would still want to do this as a just-in-case measure.</li> </ol> Other caveats/gotchas: <ol> <li>You'll also need to ensure that your category names and page names are unique. On a large site this is not always trivial (or even practical) which is probably why you see URLs like the ones here on Stack Overflow where the question id is actually in the URL, and the "page name" part is just SEO sugar.</li> <li>You'll need to have a strategy for handling name changes. If a category name or page name is changed, you'll need to have something in place to redirect links to the old names to the new ones for maximum SEO goodness. You'll also want to make sure that the new name of a category/page isn't the same as the old name of another category/page, which adds a bit more complexity to the picture.</li> </ol> All that said, it is feasible, and it it certainly worthwhile in my opinion. Especially if you expect most of your traffic to come from search engines.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSEO URLs with ASP.NET MVC
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USEric Petroelje
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.