StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9297518
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-15T16:49:03.727
FavoriteCount
0
LastActivityDate
2012-02-15T16:49:03.727
LastEditDate
LastEditorUserId
0
OwnerUserId
812837
ParentId
9296200
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
As @Shiplu pointed out, this is largely a normalization issue. Despite what some people seem to think, multi-value columns are murder to try to get right. Your basic issue is: You have members, who are interested in one or more companies/industries, which belong to one or more industries. You table structure should probably start as: <pre><code>Industry =============== id -- autoincrement name -- varchar Company ============== id -- autoincrement name -- varchar Company_Industry =============== companyId -- fk reference to Company.id industryId -- fk reference to Industry.id Member =============== id -- autoincrement name -- varchar email -- varchar Member_Interest_Industry ========================= memberId -- fk reference to Member.id industryId -- fk reference to Industry.id Member_Interest_Company ======================== memberId -- fk reference to Member.id companyId -- fk reference to Company.id </code></pre> To get all companies a member is interested in (directly, or through an industry), you can then run something like this: <pre><code>SELECT a.name, a.email, c.name FROM Member as a JOIN Member_Interest_Company as b ON b.memberId = a.id JOIN Company as c ON c.id = b.companyId WHERE a.id = :inputParm UNION SELECT a.name, a.email, d.name FROM Member as a JOIN Member_Interest_Industry as b ON b.memberId = a.id JOIN Company_Industry as c ON c.industryId = b.industryId JOIN Company as d ON d.id = c.companyId WHERE a.id = :inputParm </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConditional Select in MySQL
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USClockwork-Muse
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. 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
 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.