StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17469794
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-07-04T12:02:42.710
FavoriteCount
0
LastActivityDate
2013-07-04T12:02:42.710
LastEditDate
LastEditorUserId
0
OwnerUserId
205608
ParentId
17469172
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
It seems from your question and your tags that you're preparing to deploy a MySQL server instance on a machine that's visible from the public internet. It seems you're planning to have your desktop and mobile apps establish connections, using the MySQL protocol and using well-known MySQL server access credentials (username / password) for the purpose of registering themselves. Do Not Do This! Seriously. Instead, create a small web application on a web server than connects to your MySQL database. Arrange for your client apps to contact your web app with the information needed to register themselves. Then get the web app to carry out whatever MySQL operations are needed for registration. Put your MySQL server behind a firewall. If you have a data center or a hosting service, this is straightforward and most likely already done. If you're running your own machine (physical or virtual) set up MySQL so it's not visible from the public internet. Here's why: First, it's poor practice to make a database server visible from the public internet. It opens you up to all kinds of badguy tricks, like denial-of-service attacks and attempts to steal your users' data. Second, you'll have to burden your client applications with MySQL access protocol software. This is bloated compared to using HTTP to post a "register" request. Third, HTTP is super-lightweight compared to MySQL. Your clients send a simple request and wait for a simple response. Web servers running your app (apache, nginx, IIS, etc) are good at queueing the requests if there are a lot of them. Fourth, if you do this in a web app you can update the web app if you change your database or business rules. If you put the MySQL queries in your client apps things get much less flexible. Good luck. Be careful out there on the internet.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs Javascript a good option for providing security within a web app?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USO. Jones
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. COThank you for your help with my vague question.
 singulars
 PostPostId
 PO
 UserUserId
 USbot_bot

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.