StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18416136
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-24T07:26:07.123
FavoriteCount
0
LastActivityDate
2013-08-24T07:26:07.123
LastEditDate
LastEditorUserId
0
OwnerUserId
727208
ParentId
18415681
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
First of all, you need to redirect all your requests to a single PHP file. That part you do in .htaccess on Apache or it's counterparts on other servers. Then you need to explore what data you can see in <code>$_SERVER</code>. It's quite common to use <code>$_SERVER['PATH_INFO']</code>, but the choice will depend on how exactly you rewrite the request. Then you need to create a router, that has a list of regular expression and tries to match then against the URL fragment that you have acquired. Here are few example that might give you some ideas: <ul> <li><code>'#^/(?P<page>[^/\\\\.,;?\n]+)$#'</code></li> <li><code>'#^/user/(?P<id>[0-9]+)/(?P<nickname>[^/\.,;?\n]+)$#'</code></li> <li><code>'#^(?:/test/(?P<parameter>[^/\\\\.,;?\n]+))?/mandatory$#'</code></li> </ul> It is common practice tho have these regular expressions generated from much simpler notations, but for the first iteration you should not focus on it too much. Also, if you use expressions, that have optional fragments, you should also provide "fallback" values. These values would be used as defaults, if fragment is not provided, but pattern is matched. The way I do it all looks like this in PHP: <pre><code>/* * Routing mechanism */ $uri = isset( $_SERVER[ 'PATH_INFO' ] ) ? $_SERVER[ 'PATH_INFO' ] : '/'; $builder = new RequestBuilder; $request = $builder->create(); $request->setUri( $uri ); $router = new Router( new RouteBuilder ); $router->import( $reader->getAsArray( __DIR__ . '/config/routes.json' ) ); $router->route( $request ); </code></pre> After this the <code>$request</code> variable contains an object, which then you can query for specific parameter using commands like <code>$id = $request->getParameter('id')</code> or <code>$controller = $request->getParameter('controller')</code>. If you do not mess up with patterns themselves, then the values, that you extract will be safe against unauthorized file inclusions.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to set up a single entry point architecture similar to Laravel's?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStereško
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to set up a single entry point architecture similar to Laravel's?
 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
 VTUpMod
2. 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.