StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3160805
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-07-01T18:54:38.610
FavoriteCount
0
LastActivityDate
2010-07-01T18:54:38.610
LastEditDate
LastEditorUserId
0
OwnerUserId
253377
ParentId
3160509
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I use the following rules: <ul> <li>Always uppercase sql reserved words (SELECT, FROM, WHERE, HAVING, AND, OR, DISTINCT etc.)</li> </ul> <UL>Ugly: <code>select height,width,age from person where width = 20</code> Tidy: <code>SELECT height, width, age FROM person WHERE (width = 20)</code> </UL> <ul> <li>Lowercase all table names. Never use camelcase (donkeyWrench) in table names (you will shoot yourself in the head if you create the queries by hand).</li> <li>Always use parentheses at WHERE and HAVING clauses. Use space between operators.</li> </ul> <UL>Ugly: <code>... where width=20 and height>20</code> Tidy: <code>WHERE (width = 20) AND (height > 20)</code> </UL> <ul> <li>Use aliases for tablenames.</li> </ul> <ul> `SELECT * FROM donkeywrench dw ...` </ul> <ul> <li>Use readable, tablename related primary key fields. I always start keys and primary keys with 'id_'.</li> </ul> <ul> tablename: donkeywrench, primary key: id_donkeywrench </ul> <ul> <li>Mark where the query originated from. While reading logs you can easily track down where the problem occured.</li> </ul> <ul> /*Called from donkeykong.php, line 22*/ SELECT * FROM donkeywrench dw ... </ul> <ul> <li>If the query is loooong</li> </ul> <ul> - Always leave the operator (AND, OR) at the end of the line - Use parentheses! </ul> Example: <pre><code>/*Executed from xyz.php*/ SELECT p.height, p.width, p.age, pd.hastel, pd.hasmobile FROM person p LEFT JOIN personaldata pd ON p.id_person = pd.id_person LEFT JOIN relatives r ON pd.id_person = r.id_person WHERE ( p.width = 20 ) AND ( (p.height > 20) AND (p.height < 15) ) AND ( pd.hastel) ORDER BY p.age, p.height </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to make sure that my SQL code is not a scary mess
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJauzsika
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. COI disagree with the parentheses around WHERE conditions. When operator precedence is clear, I find it distracting. It's like writing the expression ((x * y) + (s * t)) / z instead of (x * y + s * t) / z. When there are fewer parentheses, it's easier to see how they match up. Of course, this is a matter of preference.
 singulars
 PostPostId
 PO
 UserUserId
 USJustin K

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.