StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5694806
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-04-17T16:37:04
FavoriteCount
0
LastActivityDate
2011-04-17T16:37:04
LastEditDate
LastEditorUserId
0
OwnerUserId
650492
ParentId
5693841
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Gheez listing all the best practices for MySQL would require a book. Let me first answer: <blockquote> I want the next user who registers has an age greater than all those already </blockquote> Use a trigger: <pre><code>DELIMITER $$ CREATE TRIGGER bi_account_each BEFORE INSERT ON account FOR EACH ROW BEGIN declare MaxAge integer; SELECT Max(account.age) INTO MaxAge FROM account; IF (new.age <= MaxAge) THEN BEGIN /* force an error by selecting from a table_that_does_not_exist.*/ SELECT * FROM ErrFromTrigger_bi_account_each_New_Member_Must_Be_Older_then_The_Last END; END IF; END$$ DELIMITER ; </code></pre> Or a stored function <pre><code>DELIMITER $$ CREATE FUNCTION CanInsertInAccount(pAge integer) RETURNS boolean BEGIN declare MaxAge integer; declare InsertAllowed boolean; SELECT Max(account.age) INTO MaxAge FROM account; SET InsertAllowed = (pAge > MaxAge); RETURN InsertAllowed; END$$ DELIMITER ; </code></pre> See: <a href="http://dev.mysql.com/doc/refman/5.1/en/triggers.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.1/en/triggers.html</a> For more info on triggers. And: <a href="http://dev.mysql.com/doc/refman/5.0/en/create-procedure.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.0/en/create-procedure.html</a> For more info on stored procedures and functions. As for best practices, my list would be: <ol> <li>Don't trust customer input: When inserting values from php into MySQL always use <code>mysql_real_escape_string()</code> on every value (or use PDO {prepared statements}); This will protect you from SQL-injection attacks. </li> <li>Strip HTML tags before displaying customer inputted data Disallow all HTML. Use htmlspecialchars() to convert HTML characters into HTML entities. So characters like < and > that mark the beginning/end of a tag are turned into < and >. It is not enough to simply use strip_tags() to only allow some tags as the function does not strip out harmful attributes like the onclick or onload. </li> <li>Normalize your database </li> <li>Use foreign key checks </li> <li>Use transactions, but commit (or rollback) as often as you can. Only put stuff that belongs together in one transaction. </li> <li>Use triggers </li> <li>Use stored procedures to manipulate and test stuff that depends on the layout of your database.</li> </ol> That's what I can think of right now, the list is by no means complete and these things are somewhat personal. It works for me, YMMV.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPolicy query execution
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJohan
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.