StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19840892
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-07T16:11:03.933
FavoriteCount
0
LastActivityDate
2013-11-07T16:16:14.803
LastEditDate
2013-11-07T16:16:14.803
LastEditorUserId
2558535
OwnerUserId
2558535
ParentId
19840729
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
This is my opinion: Session >> All data that you ar storing in session will be stored on the server. The default location is disk. IO - is a very limited resource. Do not start sessions when you do not need to. Do not store data in sessions when you do not need to. If you have many PHP scripts that use session variables, consider recompiling PHP using the shared memory module for sessions, or use a RAM Disk. Enable this with "configure -–with-mm" then re-compile PHP, and set session.save_handler=mm in php.ini. Supply the new page with some GET parameters.>> It is a good practice, but has one lack. If the client stores links in his favorites (and etc...) gives it to another user and he opens this link later, then he will see the success message. Supply more than the Location header and read them on the target page.>> It is a good method, but it depends on the server configuration and proxies in the middle of application and client. Sometimes the server configuration (proxies) kill non standard headers. But usually it is not a problem. Store this data in cookies.>> Lacks: Do not forget to delete cookies. All data stored in cookies will be transferred from your server to client and back. Store this data on the server. Storing in database>>, memcache, NoSQL and etc. If this does not create additional load on the server and is ideally suited for your application, why not? And you need not necessarily to store the message itself, but only a state flag. In practice I use all this methods. Which method should be used at the moment - look at the requirements for the application and its future use.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POwhat is the best way to send info back to user
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USShivanshu
UserOwnerUserId
1. USShivanshu
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POwhat is the best way to send info back to user
 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
 VTAcceptedByOriginator
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.