StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7838088
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-10-20T15:12:46.687
FavoriteCount
0
LastActivityDate
2011-10-20T15:12:46.687
LastEditDate
LastEditorUserId
0
OwnerUserId
562459
ParentId
7837347
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
You can't judge the soundness of a database design by counting tables. There's no such thing as "too many tables" normal form, or "not enough tables" normal form. There's also no such thing as "too many columns" normal form, or "not enough columns" normal form. As it stands today, having one column for each of the transmission gear ratios might still get you to 5NF. That's because it's not having multiple columns whose values come from the same domain that's a problem. It's having multiple columns whose values come from the same domain and have the same meaning that's a problem. Clearly, 8th gear and 1st gear have different meanings. In fact, you might consider them to be drawn from different domains. My guess is that 0.67 isn't a valid value for 1st gear, and that 4.85 isn't a valid value for 8th. When these are stored in different columns, <ul> <li>it's easy to enforce the constraint that every row have a value for each of the 8 transmission gear ratios, and </li> <li>constraints on the range of valid values for each gear ratio is really simple. (But you have to accommodate NULLs for later designs having only 5 or 6 gears, and that raises normalization issues.)</li> </ul> When they're stored as rows, <ul> <li>it's harder--perhaps impossible--to enforce the constraint that each vehicle have a value for each of the 8 transmission gear ratios, and</li> <li>constraints on the range of valid values for each gear ratio is more complicated. (Especially when you later accommodate designs that have only 5 or 6 gears.)</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODB tables design with a lot of attributes
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMike Sherrill 'Cat Recall'
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODB tables design with a lot of attributes
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COReally good point.
 singulars
 PostPostId
 PO
 UserUserId
 USnubm

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.