StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8160140
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-16T23:19:58.370
FavoriteCount
0
LastActivityDate
2011-11-16T23:24:58.460
LastEditDate
2011-11-16T23:24:58.460
LastEditorUserId
345585
OwnerUserId
345585
ParentId
8159740
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
While the correct way is typically accepted as URL rewriting using .htaccess as @Nathan has shown, you can also optionally use <code>MultiViews</code> on a per-directory basis: <pre><code><Directory /home/www/sitename/htdocs> Options + MultiViews </Directory> </code></pre> Multiviews, on 404 from an unknown file extension, will begin searching for a match in the filename. That is, if the URI is <code>foo</code>, it'll look for <code>foo.*</code>; that said, it could potentially find <code>foo.gif</code>, <code>foo.jpg</code>, <code>foo.html</code>, etc., and will return the highest quality option. If you're certain you could provide all your content on a unique-name basis (shouldn't be hard), then by all means use this. Then just change all your anchors to direct to <code>somepage?product=343&type=4</code> instead of <code>somepage.php?product=343&type=4</code> edit: Yes, such links can be made even cleaner. Using URL rewriting, you could rewrite your URLs to: <code>somepage/product/343/type/4</code> or <code>somepage/343/4</code> This is done by the appropriate (respective) regex: <pre><code> RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)/(.*)/(.*)/(.*)/(.*)$ $1.php?$2=$3&$4=$5 [L,QSA] </code></pre> or <pre><code> RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)/(.*)/(.*)$ $1.php?product=$2&type=$3 [L,QSA] </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POClean URL using .htaccess and possible suggestions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USstslavik
UserOwnerUserId
1. USstslavik
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.