StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7681946
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-07T00:24:33.727
FavoriteCount
0
LastActivityDate
2011-10-07T00:24:33.727
LastEditDate
LastEditorUserId
0
OwnerUserId
319085
ParentId
7681755
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Yes, you should never rely on a GET variable (or even a hidden POST variable) to say, "sure, let me in, I'm a valid user!". Personally, I would strip the GET information from the link and rely solely on session variables. Remember to place a 'session_start();' as the first line of code if you are using PHP to activate the session. For submit.php: <pre><code><?php session_start(); if ($_POST['user'] && $_POST['pass']) { // Make sure both variable are set if (your_method) { // Code to check if the user and pass are valid however you plan $_SESSION['user'] = $_POST['user']; $_SESSION['loggedin'] = time(); } } header('Location: form.php'); // Either way, pass or fail, return to form.php exit(); ?> </code></pre> Then in form.php: <pre><code><?php session_start(); $activeuser = false; if ($_SESSION['user'] && $_SESSION['loggedin'] < (time()+600)) { // Check if the user exists and the last access was with in 10 minutes. $_SESSION['loggedin'] = time(); // If so, keep them up to date! $activeuser = true; } if ($activeuser) { // whatever should show to someone logged in } else { // Show log in form } ?> </code></pre> Also, you may already know this, but the default method of transferring is GET, so be sure to specify method="post" in the form tag. It's normally best to use header() to redirect if needed as Javascript is client-side and can be avoided which can break your intent for the functioning of your site.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POI am confused about PHP Post/Redirect/Get
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USExit
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.