StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18406686
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
13
CommunityOwnedDate
CreationDate
2013-08-23T15:35:05.613
FavoriteCount
0
LastActivityDate
2018-02-19T17:06:38.970
LastEditDate
2018-02-19T17:06:38.970
LastEditorUserId
886824
OwnerUserId
886824
ParentId
18406156
PostTypeId
2
Score
164
ViewCount
0
LastEditorDisplayName
text
Body
Your rewrite rule looks almost ok. First make sure that your <code>.htaccess</code> file is in your document root (the same place as <code>index.php</code>) or it'll only affect the sub-folder it's in (and any sub-folders within that - recursively). Next make a slight change to your rule so it looks something like: <pre><code>RewriteEngine on RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ /index.php?path=$1 [NC,L,QSA] </code></pre> At the moment you're just matching on <code>.</code> which is one instance of any character, you need at least <code>.*</code> to match any number of instances of any character. The <code>$_GET['path']</code> variable will contain the fake directory structure, so <code>/mvc/module/test</code> for instance, which you can then use in index.php to determine the Controller and actions you want to perform. If you want the whole shebang installed in a sub-directory, such as <code>/mvc/</code> or <code>/framework/</code> the least complicated way to do it is to change the rewrite rule slightly to take that into account. <pre><code>RewriteRule ^(.*)$ /mvc/index.php?path=$1 [NC,L,QSA] </code></pre> And ensure that your <code>index.php</code> is in that folder whilst the <code>.htaccess</code> file is in the document root. Alternative to <code>$_GET['path']</code> (updated Feb '18) It's not actually necessary (nor even common now) to set the path as a <code>$_GET</code> variable, many frameworks will rely on <code>$_SERVER['REQUEST_URI']</code> to retrieve the same information - normally to determine which Controller to use - but the principle is exactly the same. This does simplify the <code>RewriteRule</code> slightly as you don't need to create the path parameter: <pre><code>RewriteEngine on RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^.*$ /index.php [L,QSA] </code></pre> The same rules about installing in a sub-directory still apply, e.g. <pre><code>RewriteRule ^.*$ /mvc/index.php [L,QSA] </code></pre> <hr> The flags: <code>NC</code> = No Case (not case sensitive, not really necessary since there are no characters in the pattern) <code>L</code> = Last (it'll stop rewriting at after this Rewrite so make sure it's the last thing in your list of rewrites) <code>QSA</code> = Query String Apend, just in case you've got something like <code>?like=penguins</code> on the end which you want to keep and pass to index.php.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORedirect all to index.php htaccess
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCD001
UserOwnerUserId
1. USCD001
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORedirect all to index.php htaccess
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.